mirror of
https://github.com/hanzoai/bot.git
synced 2026-11-01 07:38:30 +00:00
zeekay
acaeda400a
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.
2.1 KiB
2.1 KiB
read_when, summary, title, x-i18n
| read_when | summary | title | x-i18n | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Zalo Personal 插件：通过 zca-cli 进行 QR 登录 + 消息（插件安装 + 渠道配置 + CLI + 工具） | Zalo Personal 插件 |
|
Zalo Personal（插件）
通过插件为 HanzoBot 提供 Zalo Personal 支持，使用 zca-cli 自动化普通 Zalo 用户账户。
警告： 非官方自动化可能导致账户被暂停/封禁。使用风险自负。
命名
渠道 id 是 zalouser，以明确表示这是自动化个人 Zalo 用户账户（非官方）。我们保留 zalo 用于潜在的未来官方 Zalo API 集成。
运行位置
此插件在 Gateway 网关进程内运行。
如果你使用远程 Gateway 网关，请在运行 Gateway 网关的机器上安装/配置它，然后重启 Gateway 网关。
安装
选项 A：从 npm 安装
hanzo-bot plugins install @hanzo/bot-zalouser
之后重启 Gateway 网关。
选项 B：从本地文件夹安装（开发）
hanzo-bot plugins install ./extensions/zalouser
cd ./extensions/zalouser && pnpm install
之后重启 Gateway 网关。
前置条件：zca-cli
Gateway 网关机器必须在 PATH 中有 zca：
zca --version
配置
渠道配置位于 channels.zalouser 下（不是 plugins.entries.*）：
{
channels: {
zalouser: {
enabled: true,
dmPolicy: "pairing",
},
},
}
CLI
hanzo-bot channels login --channel zalouser
hanzo-bot channels logout --channel zalouser
hanzo-bot channels status --probe
hanzo-bot message send --channel zalouser --target <threadId> --message "Hello from HanzoBot"
hanzo-bot directory peers list --channel zalouser --query "name"
智能体工具
工具名称：zalouser
操作：send、image、link、friends、groups、me、status