bot browser

Manage 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 <controlUrl>: override browser.controlUrl for this command invocation.
• --browser-profile <name>: choose a browser profile (default comes from config).
• --json: machine-readable output (where supported).

Quick start (local)

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

Profiles

Profiles are named browser routing configs. In practice:

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

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

Use a specific profile:

bot browser --browser-profile work tabs

Tabs

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

Snapshot / screenshot / actions

Snapshot:

bot browser snapshot

Screenshot:

bot browser screenshot

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

bot browser navigate https://example.com
bot browser click <ref>
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:

bot browser extension install
bot browser extension path

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

Full guide: Chrome extension

Remote browser control (bot browser serve)

If the Gateway runs on a different machine than the browser, run a standalone browser control server on the machine that runs Chrome:

bot browser serve --bind 127.0.0.1 --port 18791 --token <token>

Then point the Gateway at it using browser.controlUrl + browser.controlToken (or BOT_BROWSER_CONTROL_TOKEN).

Security + TLS best-practices: Browser tool, Tailscale, Security