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.2 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

CLI reference for `hanzo-bot browser` (profiles, tabs, actions, extension relay)

You use `hanzo-bot browser` and want examples for common tasks

You want to control a browser running on another machine via a node host

You want to use the Chrome extension relay (attach/detach via toolbar button)

browser

`hanzo-bot browser`

Manage HanzoBot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).

Browser tool + API: Browser tool
Chrome extension relay: Chrome extension

Common flags

--url <gatewayWsUrl>: Gateway WebSocket URL (defaults to config).
--token <token>: Gateway token (if required).
--timeout <ms>: request timeout (ms).
--browser-profile <name>: choose a browser profile (default from config).
--json: machine-readable output (where supported).

Quick start (local)

hanzo-bot browser --browser-profile chrome tabs
hanzo-bot browser --browser-profile hanzo-bot start
hanzo-bot browser --browser-profile hanzo-bot open https://example.com
hanzo-bot browser --browser-profile hanzo-bot snapshot

Profiles

Profiles are named browser routing configs. In practice:

hanzo-bot: launches/attaches to a dedicated HanzoBot-managed Chrome instance (isolated user data dir).
chrome: controls your existing Chrome tab(s) via the Chrome extension relay.

hanzo-bot browser profiles
hanzo-bot browser create-profile --name work --color "#FF5A36"
hanzo-bot browser delete-profile --name work

Use a specific profile:

hanzo-bot browser --browser-profile work tabs

Tabs

hanzo-bot browser tabs
hanzo-bot browser open https://docs.hanzo-bot.ai
hanzo-bot browser focus <targetId>
hanzo-bot browser close <targetId>

Snapshot / screenshot / actions

Snapshot:

hanzo-bot browser snapshot

Screenshot:

hanzo-bot browser screenshot

Navigate/click/type (ref-based UI automation):

hanzo-bot browser navigate https://example.com
hanzo-bot browser click <ref>
hanzo-bot browser type <ref> "hello"

This mode lets the agent control an existing Chrome tab that you attach manually (it does not auto-attach).

Install the unpacked extension to a stable path:

hanzo-bot browser extension install
hanzo-bot browser extension path

Then Chrome → chrome://extensions → enable “Developer mode” → “Load unpacked” → select the printed folder.

Full guide: Chrome extension

Remote browser control (node host proxy)

If the Gateway runs on a different machine than the browser, run a node host on the machine that has Chrome/Brave/Edge/Chromium. The Gateway will proxy browser actions to that node (no separate browser control server required).

Use gateway.nodes.browser.mode to control auto-routing and gateway.nodes.browser.node to pin a specific node if multiple are connected.

Security + remote setup: Browser tool, Remote access, Tailscale, Security

3.2 KiB Raw Permalink Blame History Unescape Escape

hanzo-bot browser