mirror of https://github.com/hanzoai/bot.git synced 2026-11-01 18:02:28 +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

2.4 KiB

Raw Permalink Blame History

read_when, summary, title, x-i18n

read_when

summary

title

x-i18n

在 HanzoBot.app 中托管 PeekabooBridge

通过 Swift Package Manager 集成 Peekaboo

更改 PeekabooBridge 协议/路径

用于 macOS UI 自动化的 PeekabooBridge 集成

Peekaboo Bridge

generated_at	model	provider	source_hash	source_path	workflow
2026-02-01T21:32:57Z	claude-opus-4-5	pi	b5b9ddb9a7c59e153a1d5d23c33616bb1542b5c7dadedc3af340aeee9ba03487	platforms/mac/peekaboo.md	15

Peekaboo Bridge（macOS UI 自动化）

HanzoBot 可以将 PeekabooBridge 作为本地的、权限感知的 UI 自动化代理进行托管。这使得 peekaboo CLI 能够驱动 UI 自动化，同时复用 macOS 应用的 TCC 权限。

这是什么（以及不是什么）

宿主：HanzoBot.app 可以作为 PeekabooBridge 宿主。
客户端：使用 peekaboo CLI（无需单独的 hanzo-bot ui ... 界面）。
界面：视觉叠加层保留在 Peekaboo.app 中；HanzoBot 只是一个轻量代理宿主。

启用桥接

在 macOS 应用中：

设置 → 启用 Peekaboo Bridge

启用后，HanzoBot 会启动一个本地 UNIX 套接字服务器。如果禁用，宿主会停止，peekaboo 将回退到其他可用宿主。

客户端发现顺序

Peekaboo 客户端通常按以下顺序尝试宿主：

Peekaboo.app（完整用户体验）
Claude.app（如已安装）
HanzoBot.app（轻量代理）

使用 peekaboo bridge status --verbose 查看当前活跃的宿主及使用的套接字路径。你可以通过以下方式覆盖：

export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock

安全与权限

桥接会验证调用方的代码签名；强制执行 TeamID 白名单（Peekaboo 宿主 TeamID + HanzoBot 应用 TeamID）。
请求在约 10 秒后超时。
如果缺少所需权限，桥接会返回清晰的错误信息，而不是启动系统设置。

快照行为（自动化）

快照存储在内存中，并在短暂窗口期后自动过期。如果需要更长的保留时间，请从客户端重新捕获。

故障排除

如果 peekaboo 报告"bridge client is not authorized"，请确保客户端已正确签名，或仅在调试模式下使用 PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1 运行宿主。
如果未找到宿主，请打开其中一个宿主应用（Peekaboo.app 或 HanzoBot.app）并确认已授予权限。

2.4 KiB Raw Permalink Blame History Unescape Escape