Skip to main content

​
clawdbot browser

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

​
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)

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

​
Profiles

Profiles are named browser routing configs. In practice:
  • clawd: launches/attaches to a dedicated Clawdbot-managed Chrome instance (isolated user data dir).
  • chrome: controls your existing Chrome tab(s) via the Chrome extension relay.
clawdbot browser profiles
clawdbot browser create-profile --name work --color "#FF5A36"
clawdbot browser delete-profile --name work
Use a specific profile: 
clawdbot browser --browser-profile work tabs

​
Tabs

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

​
Snapshot / screenshot / actions

Snapshot: 
clawdbot browser snapshot
Screenshot: 
clawdbot browser screenshot
Navigate/click/type (ref-based UI automation): 
clawdbot browser navigate https://example.com
clawdbot browser click <ref>
clawdbot 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: 
clawdbot browser extension install
clawdbot 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