openclaw browser
Manage OpenClaw’s browser control surface and run browser actions (lifecycle, profiles, tabs, snapshots, screenshots, navigation, input, state emulation, and debugging).
Related:
- Browser tool + API: Browser tool
Common flags
--url <gatewayWsUrl>: Gateway WebSocket URL (defaults to config).--token <token>: Gateway token (if required).--timeout <ms>: request timeout (ms).--expect-final: wait for a final Gateway response.--browser-profile <name>: choose a browser profile (default from config).--json: machine-readable output (where supported).
Quick start (local)
Lifecycle
- For
attachOnlyand remote CDP profiles,openclaw browser stopcloses the active control session and clears temporary emulation overrides even when OpenClaw did not launch the browser process itself. - For local managed profiles,
openclaw browser stopstops the spawned browser process.
If the command is missing
Ifopenclaw browser is an unknown command, check plugins.allow in
~/.openclaw/openclaw.json.
When plugins.allow is present, the bundled browser plugin must be listed
explicitly:
browser.enabled=true does not restore the CLI subcommand when the plugin
allowlist excludes browser.
Related: Browser tool
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.
Tabs
Snapshot / screenshot / actions
Snapshot:--full-pageis for page captures only; it cannot be combined with--refor--element.existing-session/userprofiles support page screenshots and--refscreenshots from snapshot output, but not CSS--elementscreenshots.
State and storage
Viewport + emulation:Debugging
Existing Chrome via MCP
Use the built-inuser profile, or create your own existing-session profile:
- snapshot-driven actions use refs, not CSS selectors
clickis left-click onlytypedoes not supportslowly=truepressdoes not supportdelayMswait --load networkidleis not supported- screenshots support page captures and
--ref, but not CSS--element responsebody, download interception, PDF export, and batch actions still require a managed browser or raw CDP profile
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). Usegateway.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