mirror of https://github.com/hanzoai/bot.git synced 2026-10-30 17:24:26 +00:00

Files

T

zeekay acaeda400a Eradicate OpenClaw — resolve merge conflicts and finish the rebrand

Three coordinated things:

1. Resolve the committed upstream/main merge conflicts. 94 files were
   sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
   conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
   by keeping HEAD everywhere — 540 conflict blocks.

2. Rewrite remaining OpenClaw text refs.
     OPENCLAW   → HANZO_BOT
     OpenClaw   → HanzoBot          (PascalCase type identifiers)
     openclaw   → bot               (codebase convention — botToken,
                                    botUsername etc.; avoids invalid
                                    hyphenated JS identifiers)
     openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z]   (compound)
     ai.openclaw.x → ai.hanzo.bot.x  (JVM package path)

3. Delete or rename openclaw-named file paths (116 of them). Dead
   duplicates with a Bot-named canonical from the partial migration:
   deleted. Otherwise renamed.
     ai/openclaw/**           → deleted (ai/hanzo/bot/** canonical)
     Sources/OpenClaw*/       → deleted (Sources/Bot* canonical)
     Tests/OpenClawIPCTests/  → deleted (Tests/BotIPCTests canonical)
     OpenClawKit/             → deleted (BotKit canonical)
     openclaw-tools.*.ts      → deleted (bot-tools.*.ts canonical)
     openclaw-root.ts etc.    → deleted (bot-root.ts canonical)
     types.openclaw.ts        → deleted (types.bot.ts canonical)
     extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
     docs/start/openclaw.md   → renamed hanzo-bot.md (+ zh-CN)
     docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
     scripts/.../openclaw-*   → deleted (bot/hanzo-bot parallels)
     openclaw.mjs             → deleted (hanzo-bot.mjs is package.bin)

Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).

Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.

The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.

Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.

2026-05-11 17:56:29 -07:00

3.6 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Troubleshoot cron and heartbeat scheduling and delivery

Cron did not run

Cron ran but no message was delivered

Heartbeat seems silent or skipped

Automation Troubleshooting

Automation troubleshooting

Use this page for scheduler and delivery issues (cron + heartbeat).

Command ladder

hanzo-bot status
hanzo-bot gateway status
hanzo-bot logs --follow
hanzo-bot doctor
hanzo-bot channels status --probe

Then run automation checks:

hanzo-bot cron status
hanzo-bot cron list
hanzo-bot system heartbeat last

Cron not firing

hanzo-bot cron status
hanzo-bot cron list
hanzo-bot cron runs --id <jobId> --limit 20
hanzo-bot logs --follow

Good output looks like:

cron status reports enabled and a future nextWakeAtMs.
Job is enabled and has a valid schedule/timezone.
cron runs shows ok or explicit skip reason.

Common signatures:

cron: scheduler disabled; jobs will not run automatically → cron disabled in config/env.
cron: timer tick failed → scheduler tick crashed; inspect surrounding stack/log context.
reason: not-due in run output → manual run called without --force and job not due yet.

Cron fired but no delivery

hanzo-bot cron runs --id <jobId> --limit 20
hanzo-bot cron list
hanzo-bot channels status --probe
hanzo-bot logs --follow

Good output looks like:

Run status is ok.
Delivery mode/target are set for isolated jobs.
Channel probe reports target channel connected.

Common signatures:

Run succeeded but delivery mode is none → no external message is expected.
Delivery target missing/invalid (channel/to) → run may succeed internally but skip outbound.
Channel auth errors (unauthorized, missing_scope, Forbidden) → delivery blocked by channel credentials/permissions.

Heartbeat suppressed or skipped

hanzo-bot system heartbeat last
hanzo-bot logs --follow
hanzo-bot config get agents.defaults.heartbeat
hanzo-bot channels status --probe

Good output looks like:

Heartbeat enabled with non-zero interval.
Last heartbeat result is ran (or skip reason is understood).

Common signatures:

heartbeat skipped with reason=quiet-hours → outside activeHours.
requests-in-flight → main lane busy; heartbeat deferred.
empty-heartbeat-file → interval heartbeat skipped because HEARTBEAT.md has no actionable content and no tagged cron event is queued.
alerts-disabled → visibility settings suppress outbound heartbeat messages.

Timezone and activeHours gotchas

hanzo-bot config get agents.defaults.heartbeat.activeHours
hanzo-bot config get agents.defaults.heartbeat.activeHours.timezone
hanzo-bot config get agents.defaults.userTimezone || echo "agents.defaults.userTimezone not set"
hanzo-bot cron list
hanzo-bot logs --follow

Quick rules:

Config path not found: agents.defaults.userTimezone means the key is unset; heartbeat falls back to host timezone (or activeHours.timezone if set).
Cron without --tz uses gateway host timezone.
Heartbeat activeHours uses configured timezone resolution (user, local, or explicit IANA tz).
ISO timestamps without timezone are treated as UTC for cron at schedules.

Common signatures:

Jobs run at the wrong wall-clock time after host timezone changes.
Heartbeat always skipped during your daytime because activeHours.timezone is wrong.

3.6 KiB Raw Permalink Blame History

Automation troubleshooting

Command ladder

Cron not firing

Cron fired but no delivery

Heartbeat suppressed or skipped

Timezone and activeHours gotchas

3.6 KiB

Raw Permalink Blame History