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.
4.6 KiB
read_when, summary, title, x-i18n
| read_when | summary | title | x-i18n | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
为 Gateway 网关仪表盘集成 Tailscale Serve/Funnel | Tailscale |
|
Tailscale(Gateway 网关仪表盘)
HanzoBot 可以为 Gateway 网关仪表盘和 WebSocket 端口自动配置 Tailscale Serve(tailnet)或 Funnel(公共)。这使 Gateway 网关保持绑定到 loopback,同时 Tailscale 提供 HTTPS、路由和(对于 Serve)身份头。
模式
serve:仅限 Tailnet 的 Serve,通过tailscale serve。Gateway 网关保持在127.0.0.1上。funnel:通过tailscale funnel的公共 HTTPS。HanzoBot 需要共享密码。off:默认(无 Tailscale 自动化)。
认证
设置 gateway.auth.mode 来控制握手:
token(设置BOT_GATEWAY_TOKEN时的默认值)password(通过BOT_GATEWAY_PASSWORD或配置的共享密钥)
当 tailscale.mode = "serve" 且 gateway.auth.allowTailscale 为 true 时,
有效的 Serve 代理请求可以通过 Tailscale 身份头(tailscale-user-login)进行认证,无需提供令牌/密码。HanzoBot 通过本地 Tailscale 守护进程(tailscale whois)解析 x-forwarded-for 地址并将其与头匹配来验证身份,然后才接受它。
HanzoBot 仅在请求从 loopback 到达并带有 Tailscale 的 x-forwarded-for、x-forwarded-proto 和 x-forwarded-host 头时才将其视为 Serve 请求。
要要求显式凭证,设置 gateway.auth.allowTailscale: false 或强制 gateway.auth.mode: "password"。
配置示例
仅限 Tailnet(Serve)
{
gateway: {
bind: "loopback",
tailscale: { mode: "serve" },
},
}
打开:https://<magicdns>/(或你配置的 gateway.controlUi.basePath)
仅限 Tailnet(绑定到 Tailnet IP)
当你希望 Gateway 网关直接监听 Tailnet IP 时使用此方式(无 Serve/Funnel)。
{
gateway: {
bind: "tailnet",
auth: { mode: "token", token: "your-token" },
},
}
从另一个 Tailnet 设备连接:
- 控制 UI:
http://<tailscale-ip>:18789/ - WebSocket:
ws://<tailscale-ip>:18789
注意:在此模式下 loopback(http://127.0.0.1:18789)将不工作。
公共互联网(Funnel + 共享密码)
{
gateway: {
bind: "loopback",
tailscale: { mode: "funnel" },
auth: { mode: "password", password: "replace-me" },
},
}
优先使用 BOT_GATEWAY_PASSWORD 而不是将密码提交到磁盘。
CLI 示例
hanzo-bot gateway --tailscale serve
hanzo-bot gateway --tailscale funnel --auth password
注意事项
- Tailscale Serve/Funnel 需要安装并登录
tailscaleCLI。 tailscale.mode: "funnel"除非认证模式为password,否则拒绝启动,以避免公共暴露。- 如果你希望 HanzoBot 在关闭时撤销
tailscale serve或tailscale funnel配置,设置gateway.tailscale.resetOnExit。 gateway.bind: "tailnet"是直接 Tailnet 绑定(无 HTTPS,无 Serve/Funnel)。gateway.bind: "auto"优先 loopback;如果你想要仅 Tailnet,使用tailnet。- Serve/Funnel 仅暴露 Gateway 网关控制 UI + WS。节点通过相同的 Gateway 网关 WS 端点连接,因此 Serve 可以用于节点访问。
浏览器控制(远程 Gateway 网关 + 本地浏览器)
如果你在一台机器上运行 Gateway 网关但想在另一台机器上驱动浏览器, 在浏览器机器上运行一个节点主机并让两者保持在同一个 tailnet 上。 Gateway 网关会将浏览器操作代理到节点;不需要单独的控制服务器或 Serve URL。
避免将 Funnel 用于浏览器控制;将节点配对视为操作者访问。
Tailscale 前提条件 + 限制
- Serve 需要为你的 tailnet 启用 HTTPS;如果缺少,CLI 会提示。
- Serve 注入 Tailscale 身份头;Funnel 不会。
- Funnel 需要 Tailscale v1.38.3+、MagicDNS、启用 HTTPS 和 funnel 节点属性。
- Funnel 仅支持通过 TLS 的端口
443、8443和10000。 - macOS 上的 Funnel 需要开源 Tailscale 应用变体。
了解更多
- Tailscale Serve 概述:https://tailscale.com/kb/1312/serve
tailscale serve命令:https://tailscale.com/kb/1242/tailscale-serve- Tailscale Funnel 概述:https://tailscale.com/kb/1223/tailscale-funnel
tailscale funnel命令:https://tailscale.com/kb/1311/tailscale-funnel