Browser
CLI reference for openclaw browser (profiles, tabs, actions, extension relay).
Manage OpenClaw's browser control server and run browser actions (tabs, snapshots, screenshots, navigation, click, type).
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 (milliseconds).
- ''--browser-profile <name>'': Select browser profile (default from config).
- ''--json'': Machine-readable output (if supported).
Quick start (local)
openclaw browser --browser-profile chrome tabs openclaw browser --browser-profile openclaw start openclaw browser --browser-profile openclaw open https://example.com openclaw browser --browser-profile openclaw snapshot
Profiles
Profiles are named browser routing configurations. In practice:
- ''openclaw'': Launch/attach to a dedicated OpenClaw-managed Chrome instance (isolated user data directory).
- ''chrome'': Control your existing Chrome tabs via Chrome extension relay.
openclaw browser profiles openclaw browser create-profile --name work --color "#FF5A36" openclaw browser delete-profile --name work
Use a specific profile:
openclaw browser --browser-profile work tabs
Tabs
openclaw browser tabs openclaw browser open https://docs.openclaw.ai openclaw browser focus <targetId> openclaw browser close <targetId>
Snapshot/Screenshot/Actions
Snapshot:
openclaw browser snapshot
Screenshot:
openclaw browser screenshot
Navigate/Click/Type (ref-based UI automation):
openclaw browser navigate https://example.com openclaw browser click <ref> openclaw browser type <ref> "hello"
Chrome extension relay (attach via toolbar button)
This mode lets agents control existing Chrome tabs you manually attach (does not auto-attach).
Install unpacked extension to a stable path:
openclaw browser extension install openclaw browser extension path
Then Chrome β ''chrome://extensions'' β Enable "Developer mode" β "Load unpacked" β Select 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 with Chrome/Brave/Edge/Chromium. The gateway will proxy browser actions to that node (no separate browser control server needed).
If multiple nodes are connected, use ''gateway.nodes.browser.mode'' to control auto-routing and ''gateway.nodes.browser.node'' to pin a specific node.
Security + remote setup: ''Browser tool'', ''Remote access'', ''Tailscale'', ''Security''