Files
bot/docs/zh-CN/web/dashboard.md
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.5 KiB
Raw Permalink Blame History

read_when, summary, title, x-i18n
read_when summary title x-i18n
更改仪表板认证或暴露模式
Gateway 网关仪表板(控制 UI)访问和认证 仪表板
generated_at model provider source_hash source_path workflow
2026-02-03T10:13:14Z claude-opus-4-5 pi e6876d50e17d3dd741471ed78bef6ac175b2fdbdc1c45dd52d9d2bd013e17f31 web/dashboard.md 15

仪表板(控制 UI)

Gateway 网关仪表板是默认在 / 提供的浏览器控制 UI (通过 gateway.controlUi.basePath 覆盖)。

快速打开(本地 Gateway 网关):

关键参考:

  • 控制 UI 了解使用方法和 UI 功能。
  • Tailscale 了解 Serve/Funnel 自动化。
  • Web 界面 了解绑定模式和安全注意事项。

认证通过 connect.params.auth(token 或密码)在 WebSocket 握手时强制执行。 参见 Gateway 网关配置 中的 gateway.auth。

安全注意事项:控制 UI 是一个管理界面(聊天、配置、执行审批)。 不要公开暴露它。UI 在首次加载后将 token 存储在 localStorage 中。 优先使用 localhost、Tailscale Serve 或 SSH 隧道。

快速路径(推荐)

  • 新手引导后,CLI 现在会自动打开带有你的 token 的仪表板,并打印相同的带 token 链接。
  • 随时重新打开:hanzo-bot dashboard(复制链接,如果可能则打开浏览器,如果是无头环境则显示 SSH 提示)。
  • token 保持本地(仅查询参数);UI 在首次加载后移除它并保存到 localStorage。

Token 基础(本地 vs 远程)

  • Localhost:打开 http://127.0.0.1:18789/。如果你看到"unauthorized",运行 hanzo-bot dashboard 并使用带 token 的链接(?token=...)。
  • Token 来源:gateway.auth.token(或 BOT_GATEWAY_TOKEN);UI 在首次加载后存储它。
  • 非 localhost:使用 Tailscale Serve(如果 gateway.auth.allowTailscale: true 则无需 token)、带 token 的 tailnet 绑定,或 SSH 隧道。参见 Web 界面。

如果你看到"unauthorized" / 1008

  • 运行 hanzo-bot dashboard 获取新的带 token 链接。
  • 确保 Gateway 网关可达(本地:hanzo-bot status;远程:SSH 隧道 ssh -N -L 18789:127.0.0.1:18789 user@host 然后打开 http://127.0.0.1:18789/?token=...)。
  • 在仪表板设置中,粘贴你在 gateway.auth.token(或 BOT_GATEWAY_TOKEN)中配置的相同 token。