zeekay
4bdc9ee3e4
Comprehensive rename of all openclaw references to hanzo-bot equivalents: - Package: openclaw → @hanzo/bot - Binary: openclaw → hanzo-bot - Types: OpenClaw* → Bot* - Env vars: OPENCLAW_* → BOT_* - Android: ai.openclaw.android → ai.hanzo.bot.android - iOS/macOS: ai.openclaw.* → ai.hanzo.* - Swift modules: OpenClaw* → Bot* - Plugins: openclaw.plugin.json → bot.plugin.json - Paths: .openclaw/ → .hanzo/bot/ - URLs: github.com/openclaw → github.com/hanzoai
3.2 KiB
summary, read_when, title
| summary | read_when | title | |||
|---|---|---|---|---|---|
| CLI reference for `hanzo-bot browser` (profiles, tabs, actions, extension relay) |
|
browser |
hanzo-bot browser
Manage Hanzo Bot’s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
Related:
- 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:
bot: launches/attaches to a dedicated Hanzo Bot-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
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"
Chrome extension relay (attach via toolbar button)
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