Skip to content
RemoteClaw

browser

remoteclaw browser

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

Terminal window
remoteclaw browser profiles
remoteclaw browser --browser-profile remoteclaw start
remoteclaw browser --browser-profile remoteclaw open https://example.com
remoteclaw browser --browser-profile remoteclaw snapshot

Profiles

Profiles are named browser routing configs. In practice:

  • remoteclaw: launches or attaches to a dedicated RemoteClaw-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.
Terminal window
remoteclaw browser profiles
remoteclaw browser create-profile --name work --color "#FF5A36"
remoteclaw browser create-profile --name chrome-live --driver existing-session
remoteclaw browser delete-profile --name work

Use a specific profile:

Terminal window
remoteclaw browser --browser-profile work tabs

Tabs

Terminal window
remoteclaw browser tabs
remoteclaw browser open https://docs.remoteclaw.org
remoteclaw browser focus <targetId>
remoteclaw browser close <targetId>

Snapshot / screenshot / actions

Snapshot:

Terminal window
remoteclaw browser snapshot

Screenshot:

Terminal window
remoteclaw browser screenshot

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

Terminal window
remoteclaw browser navigate https://example.com
remoteclaw browser click <ref>
remoteclaw browser type <ref> "hello"

Existing Chrome via MCP

Use the built-in user profile, or create your own existing-session profile:

Terminal window
remoteclaw browser --browser-profile user tabs
remoteclaw browser create-profile --name chrome-live --driver existing-session
remoteclaw browser create-profile --name brave-live --driver existing-session --user-data-dir "~/Library/Application Support/BraveSoftware/Brave-Browser"
remoteclaw browser --browser-profile chrome-live tabs

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