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

7.0 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Fast channel level troubleshooting with per channel failure signatures and fixes

Channel transport says connected but replies fail

You need channel specific checks before deep provider docs

Channel Troubleshooting

Channel troubleshooting

Use this page when a channel connects but behavior is wrong.

Command ladder

Run these in order first:

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

Healthy baseline:

Runtime: running
RPC probe: ok
Channel probe shows connected/ready

WhatsApp failure signatures

Symptom	Fastest check	Fix
Connected but no DM replies	`hanzo-bot pairing list whatsapp`	Approve sender or switch DM policy/allowlist.
Group messages ignored	Check `requireMention` + mention patterns in config	Mention the bot or relax mention policy for that group.
Random disconnect/relogin loops	`hanzo-bot channels status --probe` + logs	Re-login and verify credentials directory is healthy.

Full troubleshooting: /channels/whatsapp#troubleshooting-quick

Telegram failure signatures

Symptom	Fastest check	Fix
`/start` but no usable reply flow	`hanzo-bot pairing list telegram`	Approve pairing or change DM policy.
Bot online but group stays silent	Verify mention requirement and bot privacy mode	Disable privacy mode for group visibility or mention bot.
Send failures with network errors	Inspect logs for Telegram API call failures	Fix DNS/IPv6/proxy routing to `api.telegram.org`.
Upgraded and allowlist blocks you	`hanzo-bot security audit` and config allowlists	Run `hanzo-bot doctor --fix` or replace `@username` with numeric sender IDs.

Full troubleshooting: /channels/telegram#troubleshooting

Discord

Discord failure signatures

Symptom	Fastest check	Fix
Bot online but no guild replies	`hanzo-bot channels status --probe`	Allow guild/channel and verify message content intent.
Group messages ignored	Check logs for mention gating drops	Mention bot or set guild/channel `requireMention: false`.
DM replies missing	`hanzo-bot pairing list discord`	Approve DM pairing or adjust DM policy.

Full troubleshooting: /channels/discord#troubleshooting

Slack

Slack failure signatures

Symptom	Fastest check	Fix
Socket mode connected but no responses	`hanzo-bot channels status --probe`	Verify app token + bot token and required scopes.
DMs blocked	`hanzo-bot pairing list slack`	Approve pairing or relax DM policy.
Channel message ignored	Check `groupPolicy` and channel allowlist	Allow the channel or switch policy to `open`.

Full troubleshooting: /channels/slack#troubleshooting

iMessage and BlueBubbles

iMessage and BlueBubbles failure signatures

Symptom	Fastest check	Fix
No inbound events	Verify webhook/server reachability and app permissions	Fix webhook URL or BlueBubbles server state.
Can send but no receive on macOS	Check macOS privacy permissions for Messages automation	Re-grant TCC permissions and restart channel process.
DM sender blocked	`hanzo-bot pairing list imessage` or `hanzo-bot pairing list bluebubbles`	Approve pairing or update allowlist.

Full troubleshooting:

Signal

Signal failure signatures

Symptom	Fastest check	Fix
Daemon reachable but bot silent	`hanzo-bot channels status --probe`	Verify `signal-cli` daemon URL/account and receive mode.
DM blocked	`hanzo-bot pairing list signal`	Approve sender or adjust DM policy.
Group replies do not trigger	Check group allowlist and mention patterns	Add sender/group or loosen gating.

Full troubleshooting: /channels/signal#troubleshooting

Matrix

Matrix failure signatures

Symptom	Fastest check	Fix
Logged in but ignores room messages	`hanzo-bot channels status --probe`	Check `groupPolicy` and room allowlist.
DMs do not process	`hanzo-bot pairing list matrix`	Approve sender or adjust DM policy.
Encrypted rooms fail	Verify crypto module and encryption settings	Enable encryption support and rejoin/sync room.

Full troubleshooting: /channels/matrix#troubleshooting

7.0 KiB Raw Permalink Blame History