mirror of
https://github.com/hanzoai/bot.git
synced 2026-11-01 18:02:28 +00:00
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.
3.8 KiB
3.8 KiB
read_when, summary, title, x-i18n
| read_when | summary | title | x-i18n | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Mattermost 机器人设置和 HanzoBot 配置 | Mattermost |
|
Mattermost(插件)
状态:通过插件支持(bot token + WebSocket 事件)。支持频道、群组和私信。 Mattermost 是一个可自托管的团队消息平台;有关产品详情和下载,请访问官方网站 mattermost.com。
需要插件
Mattermost 以插件形式提供,不包含在核心安装中。
通过 CLI 安装(npm 注册表):
hanzo-bot plugins install @hanzo/bot-mattermost
本地检出(从 git 仓库运行时):
hanzo-bot plugins install ./extensions/mattermost
如果你在配置/新手引导期间选择 Mattermost 并检测到 git 检出,HanzoBot 会自动提供本地安装路径。
详情:插件
快速设置
- 安装 Mattermost 插件。
- 创建 Mattermost bot 账户并复制 bot token。
- 复制 Mattermost 基础 URL(例如
https://chat.example.com)。 - 配置 HanzoBot 并启动 Gateway 网关。
最小配置:
{
channels: {
mattermost: {
enabled: true,
botToken: "mm-token",
baseUrl: "https://chat.example.com",
dmPolicy: "pairing",
},
},
}
环境变量(默认账户)
如果你偏好使用环境变量,请在 Gateway 网关主机上设置:
MATTERMOST_BOT_TOKEN=...MATTERMOST_URL=https://chat.example.com
环境变量仅适用于默认账户(default)。其他账户必须使用配置值。
聊天模式
Mattermost 自动响应私信。频道行为由 chatmode 控制:
oncall(默认):仅在频道中被 @提及时响应。onmessage:响应每条频道消息。onchar:当消息以触发前缀开头时响应。
配置示例:
{
channels: {
mattermost: {
chatmode: "onchar",
oncharPrefixes: [">", "!"],
},
},
}
注意事项:
onchar仍会响应显式 @提及。channels.mattermost.requireMention对旧配置仍然有效,但推荐使用chatmode。
访问控制(私信)
- 默认:
channels.mattermost.dmPolicy = "pairing"(未知发送者会收到配对码)。 - 通过以下方式批准:
hanzo-bot pairing list mattermosthanzo-bot pairing approve mattermost <CODE>
- 公开私信:
channels.mattermost.dmPolicy="open"加上channels.mattermost.allowFrom=["*"]。
频道(群组)
- 默认:
channels.mattermost.groupPolicy = "allowlist"(提及限制)。 - 使用
channels.mattermost.groupAllowFrom将发送者加入允许列表(用户 ID 或@username)。 - 开放频道:
channels.mattermost.groupPolicy="open"(提及限制)。
出站投递目标
在 hanzo-bot message send 或 cron/webhooks 中使用这些目标格式:
channel:<id>用于频道user:<id>用于私信@username用于私信(通过 Mattermost API 解析)
裸 ID 被视为频道。
多账户
Mattermost 支持在 channels.mattermost.accounts 下配置多个账户:
{
channels: {
mattermost: {
accounts: {
default: { name: "Primary", botToken: "mm-token", baseUrl: "https://chat.example.com" },
alerts: { name: "Alerts", botToken: "mm-token-2", baseUrl: "https://alerts.example.com" },
},
},
},
}
故障排除
- 频道中无回复:确保 bot 在频道中并提及它(oncall),使用触发前缀(onchar),或设置
chatmode: "onmessage"。 - 认证错误:检查 bot token、基础 URL 以及账户是否已启用。
- 多账户问题:环境变量仅适用于
default账户。