Skip to main content

​
openclaw browser

Manage OpenClaw’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)

​
Profiles

Profiles are named browser routing configs. In practice:
  • openclaw: launches or attaches to a dedicated OpenClaw-managed Chrome instance (isolated user data dir).
  • user: controls your existing signed-in Chrome session via Chrome DevTools MCP.
  • custom CDP profiles: point at a local or remote CDP endpoint.
Use a specific profile:

​
Tabs

​
Snapshot / screenshot / actions

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

​
Existing Chrome via MCP

Use the built-in user profile, or create your own existing-session profile:
This path is host-only. For Docker, headless servers, Browserless, or other remote setups, use a CDP profile instead.

​
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