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

1.8 KiB
Raw Permalink Blame History

read_when, summary, title, x-i18n
read_when summary title x-i18n
你正在批准设备配对请求
你需要轮换或撤销设备 token
`hanzo-bot devices` 的 CLI 参考(设备配对 + token 轮换/撤销) devices
generated_at model provider source_hash source_path workflow
2026-02-03T07:44:52Z claude-opus-4-5 pi 52f903817d2886c1dc29b85d30168d1edff7944bd120a1e139159c9d99a1f517 cli/devices.md 15

hanzo-bot devices

管理设备配对请求和设备范围的 token。

命令

hanzo-bot devices list

列出待处理的配对请求和已配对的设备。

hanzo-bot devices list
hanzo-bot devices list --json

hanzo-bot devices approve <requestId>

批准待处理的设备配对请求。

hanzo-bot devices approve <requestId>

hanzo-bot devices reject <requestId>

拒绝待处理的设备配对请求。

hanzo-bot devices reject <requestId>

hanzo-bot devices rotate --device <id> --role <role> [--scope <scope...>]

为特定角色轮换设备 token(可选更新 scope)。

hanzo-bot devices rotate --device <deviceId> --role operator --scope operator.read --scope operator.write

hanzo-bot devices revoke --device <id> --role <role>

为特定角色撤销设备 token。

hanzo-bot devices revoke --device <deviceId> --role node

通用选项

  • --url <url>:Gateway 网关 WebSocket URL(配置后默认使用 gateway.remote.url)。
  • --token <token>:Gateway 网关 token(如需要)。
  • --password <password>:Gateway 网关密码(密码认证)。
  • --timeout <ms>:RPC 超时。
  • --json:JSON 输出(推荐用于脚本)。

注意事项

  • Token 轮换会返回新 token(敏感信息)。请像对待密钥一样对待它。
  • 这些命令需要 operator.pairing(或 operator.admin)scope。