coderClaw

coderclaw browser

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

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 (ms).
• --browser-profile <name>: choose a browser profile (default from config).
• --json: machine-readable output (where supported).

Quick start (local)

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

Profiles

Profiles are named browser routing configs. In practice:

• coderclaw: launches/attaches to a dedicated CoderClaw-managed Chrome instance (isolated user data dir).
• chrome: controls your existing Chrome tab(s) via the Chrome extension relay.

coderclaw browser profiles
coderclaw browser create-profile --name work --color "#FF5A36"
coderclaw browser delete-profile --name work

Use a specific profile:

coderclaw browser --browser-profile work tabs

Tabs

coderclaw browser tabs
coderclaw browser open https://docs.coderclaw.ai
coderclaw browser focus <targetId>
coderclaw browser close <targetId>

Snapshot / screenshot / actions

Snapshot:

coderclaw browser snapshot

Screenshot:

coderclaw browser screenshot

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

coderclaw browser navigate https://example.com
coderclaw browser click <ref>
coderclaw 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:

coderclaw browser extension install
coderclaw 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

This site is open source. Improve this page.