Files
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.3 KiB

read_when, summary, title, x-i18n
read_when summary title x-i18n
你想为 HanzoBot 选择一个聊天渠道
你需要快速了解支持的消息平台
HanzoBot 可连接的消息平台 聊天渠道
generated_at model provider source_hash source_path workflow
2026-02-03T07:43:27Z claude-opus-4-5 pi 2632863def6dee97e0fa8b931762f0969174fd4fb22303a00dcd46527fe4a141 channels/index.md 15

聊天渠道

HanzoBot 可以在你已经使用的任何聊天应用上与你交流。每个渠道通过 Gateway 网关连接。 所有渠道都支持文本;媒体和表情回应的支持因渠道而异。

支持的渠道

  • BlueBubbles — 推荐用于 iMessage;使用 BlueBubbles macOS 服务器 REST API,功能完整(编辑、撤回、特效、回应、群组管理——编辑功能在 macOS 26 Tahoe 上目前不可用)。
  • Discord — Discord Bot API + Gateway;支持服务器、频道和私信。
  • 飞书 — 飞书(Lark)机器人(插件,需单独安装)。
  • Google Chat — 通过 HTTP webhook 的 Google Chat API 应用。
  • iMessage(旧版) — 通过 imsg CLI 的旧版 macOS 集成(已弃用,新设置请使用 BlueBubbles)。
  • LINE — LINE Messaging API 机器人(插件,需单独安装)。
  • Matrix — Matrix 协议(插件,需单独安装)。
  • Mattermost — Bot API + WebSocket;频道、群组、私信(插件,需单独安装)。
  • Microsoft Teams — Bot Framework;企业支持(插件,需单独安装)。
  • Nextcloud Talk — 通过 Nextcloud Talk 的自托管聊天(插件,需单独安装)。
  • Nostr — 通过 NIP-04 的去中心化私信(插件,需单独安装)。
  • Signal — signal-cli;注重隐私。
  • Slack — Bolt SDK;工作区应用。
  • Telegram — 通过 grammY 使用 Bot API;支持群组。
  • Tlon — 基于 Urbit 的消息应用(插件,需单独安装)。
  • Twitch — 通过 IRC 连接的 Twitch 聊天(插件,需单独安装)。
  • WebChat — 基于 WebSocket 的 Gateway 网关 WebChat 界面。
  • WhatsApp — 最受欢迎;使用 Baileys,需要二维码配对。
  • Zalo — Zalo Bot API;越南流行的消息应用(插件,需单独安装)。
  • Zalo Personal — 通过二维码登录的 Zalo 个人账号(插件,需单独安装)。

注意事项

  • 渠道可以同时运行;配置多个渠道后,HanzoBot 会按聊天进行路由。
  • 最快的设置方式通常是 Telegram(简单的机器人令牌)。WhatsApp 需要二维码配对, 并在磁盘上存储更多状态。
  • 群组行为因渠道而异;参见群组。
  • 为安全起见,私信配对和允许列表会被强制执行;参见安全。
  • Telegram 内部机制:grammY 说明。
  • 故障排除:渠道故障排除。
  • 模型提供商单独记录;参见模型提供商。