Kurahi browser

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

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

Profiles

Profiles are named browser routing configs. In practice:

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

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

Use a specific profile:

kurahi browser --browser-profile work tabs

Tabs

kurahi browser tabs
kurahi browser open https://kodasoken.com/kolo
kurahi browser focus <targetId>
kurahi browser close <targetId>

Snapshot / screenshot / actions

Snapshot:

kurahi browser snapshot

Screenshot:

kurahi browser screenshot

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

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

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