mirror of https://github.com/hanzoai/bot.git synced 2026-10-30 17:24:26 +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

3.0 KiB

Raw Permalink Blame History

read_when, summary, title, x-i18n

read_when

summary

title

x-i18n

你想通过 Tailscale 访问 Gateway 网关

你想使用浏览器 Control UI 和配置编辑

Gateway 网关 Web 界面：Control UI、绑定模式和安全

Web

generated_at	model	provider	source_hash	source_path	workflow
2026-02-03T10:13:29Z	claude-opus-4-5	pi	4da8bc9831018c482ac918a759b9739f75ca130f70993f81911818bc60a685d1	web/index.md	15

Web（Gateway 网关）

Gateway 网关从与 Gateway 网关 WebSocket 相同的端口提供一个小型浏览器 Control UI（Vite + Lit）：

默认：http://<host>:18789/
可选前缀：设置 gateway.controlUi.basePath（例如 /hanzo-bot）

功能详见 Control UI。本页重点介绍绑定模式、安全和面向 Web 的界面。

Webhooks

当 hooks.enabled=true 时，Gateway 网关还在同一 HTTP 服务器上公开一个小型 webhook 端点。参见 Gateway 网关配置 → hooks 了解认证 + 载荷。

配置（默认开启）

当资源存在时（dist/control-ui），Control UI 默认启用。你可以通过配置控制它：

{
  gateway: {
    controlUi: { enabled: true, basePath: "/hanzo-bot" }, // basePath 可选
  },
}

Tailscale 访问

集成 Serve（推荐）

保持 Gateway 网关在本地回环上，让 Tailscale Serve 代理它：

{
  gateway: {
    bind: "loopback",
    tailscale: { mode: "serve" },
  },
}

然后启动 Gateway 网关：

hanzo-bot gateway

打开：

https://<magicdns>/（或你配置的 gateway.controlUi.basePath）

Tailnet 绑定 + 令牌

{
  gateway: {
    bind: "tailnet",
    controlUi: { enabled: true },
    auth: { mode: "token", token: "your-token" },
  },
}

然后启动 Gateway 网关（非本地回环绑定需要令牌）：

hanzo-bot gateway

打开：

http://<tailscale-ip>:18789/（或你配置的 gateway.controlUi.basePath）

公共互联网（Funnel）

{
  gateway: {
    bind: "loopback",
    tailscale: { mode: "funnel" },
    auth: { mode: "password" }, // 或 BOT_GATEWAY_PASSWORD
  },
}

安全注意事项

Gateway 网关认证默认是必需的（令牌/密码或 Tailscale 身份头）。
非本地回环绑定仍然需要共享令牌/密码（gateway.auth 或环境变量）。
向导默认生成 Gateway 网关令牌（即使在本地回环上）。
UI 发送 connect.params.auth.token 或 connect.params.auth.password。
使用 Serve 时，当 gateway.auth.allowTailscale 为 true 时，Tailscale 身份头可以满足认证（无需令牌/密码）。设置 gateway.auth.allowTailscale: false 以要求显式凭证。参见 Tailscale 和安全。
gateway.tailscale.mode: "funnel" 需要 gateway.auth.mode: "password"（共享密码）。

构建 UI

Gateway 网关从 dist/control-ui 提供静态文件。使用以下命令构建：

pnpm ui:build # 首次运行时自动安装 UI 依赖

3.0 KiB Raw Permalink Blame History Unescape Escape