bot/docs/channels/index.md at main

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.1 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Messaging platforms HanzoBot can connect to

You want to choose a chat channel for HanzoBot

You need a quick overview of supported messaging platforms

Chat Channels

HanzoBot can talk to you on any chat app you already use. Each channel connects via the Gateway. Text is supported everywhere; media and reactions vary by channel.

Supported channels

BlueBubbles — Recommended for iMessage; uses the BlueBubbles macOS server REST API with full feature support (edit, unsend, effects, reactions, group management — edit currently broken on macOS 26 Tahoe).
Discord — Discord Bot API + Gateway; supports servers, channels, and DMs.
Feishu — Feishu/Lark bot via WebSocket (plugin, installed separately).
Google Chat — Google Chat API app via HTTP webhook.
iMessage (legacy) — Legacy macOS integration via imsg CLI (deprecated, use BlueBubbles for new setups).
IRC — Classic IRC servers; channels + DMs with pairing/allowlist controls.
LINE — LINE Messaging API bot (plugin, installed separately).
Matrix — Matrix protocol (plugin, installed separately).
Mattermost — Bot API + WebSocket; channels, groups, DMs (plugin, installed separately).
Microsoft Teams — Bot Framework; enterprise support (plugin, installed separately).
Nextcloud Talk — Self-hosted chat via Nextcloud Talk (plugin, installed separately).
Nostr — Decentralized DMs via NIP-04 (plugin, installed separately).
Signal — signal-cli; privacy-focused.
Synology Chat — Synology NAS Chat via outgoing+incoming webhooks (plugin, installed separately).
Slack — Bolt SDK; workspace apps.
Telegram — Bot API via grammY; supports groups.
Tlon — Urbit-based messenger (plugin, installed separately).
Twitch — Twitch chat via IRC connection (plugin, installed separately).
WebChat — Gateway WebChat UI over WebSocket.
WhatsApp — Most popular; uses Baileys and requires QR pairing.
Zalo — Zalo Bot API; Vietnam's popular messenger (plugin, installed separately).
Zalo Personal — Zalo personal account via QR login (plugin, installed separately).

Notes

Channels can run simultaneously; configure multiple and HanzoBot will route per chat.
Fastest setup is usually Telegram (simple bot token). WhatsApp requires QR pairing and stores more state on disk.
Group behavior varies by channel; see Groups.
DM pairing and allowlists are enforced for safety; see Security.
Troubleshooting: Channel troubleshooting.
Model providers are documented separately; see Model Providers.

3.1 KiB Raw Permalink Blame History

Chat Channels

Supported channels

Notes

3.1 KiB

Raw Permalink Blame History