2026-01-15 05:30:02 +00:00
---
2026-01-27 03:23:42 +00:00
summary: "CLI reference for `clawdbot browser` (profiles, tabs, actions, extension relay)"
2026-01-15 05:30:02 +00:00
read_when:
- You use `clawdbot browser` and want examples for common tasks
2026-01-27 03:23:42 +00:00
- You want to control a browser running on another machine via a node host
2026-01-15 05:30:02 +00:00
- You want to use the Chrome extension relay (attach/detach via toolbar button)
---
# `clawdbot browser`
Manage Clawdbot’ s browser control server and run browser actions (tabs, snapshots, screenshots, navigation, clicks, typing).
Related:
- Browser tool + API: [Browser tool ](/tools/browser )
- Chrome extension relay: [Chrome extension ](/tools/chrome-extension )
## Common flags
2026-01-27 03:23:42 +00:00
- `--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).
2026-01-15 05:30:02 +00:00
- `--json` : machine-readable output (where supported).
## Quick start (local)
```bash
2026-01-15 08:50:08 +00:00
clawdbot browser --browser-profile chrome tabs
clawdbot browser --browser-profile clawd start
clawdbot browser --browser-profile clawd open https://example.com
clawdbot browser --browser-profile clawd snapshot
2026-01-15 05:30:02 +00:00
```
## Profiles
2026-01-15 08:26:23 +00:00
Profiles are named browser routing configs. In practice:
- `clawd` : launches/attaches to a dedicated Clawdbot-managed Chrome instance (isolated user data dir).
- `chrome` : controls your existing Chrome tab(s) via the Chrome extension relay.
2026-01-15 05:30:02 +00:00
```bash
clawdbot browser profiles
clawdbot browser create-profile --name work --color "#FF5A36 "
clawdbot browser delete-profile --name work
```
Use a specific profile:
```bash
clawdbot browser --browser-profile work tabs
```
## Tabs
```bash
clawdbot browser tabs
clawdbot browser open https://docs.clawd.bot
clawdbot browser focus < targetId >
clawdbot browser close < targetId >
```
## Snapshot / screenshot / actions
Snapshot:
```bash
clawdbot browser snapshot
```
Screenshot:
```bash
clawdbot browser screenshot
```
Navigate/click/type (ref-based UI automation):
```bash
clawdbot browser navigate https://example.com
clawdbot browser click < ref >
clawdbot 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:
```bash
clawdbot browser extension install
clawdbot browser extension path
```
Then Chrome → `chrome://extensions` → enable “Developer mode” → “Load unpacked” → select the printed folder.
Full guide: [Chrome extension ](/tools/chrome-extension )
2026-01-27 03:23:42 +00:00
## Remote browser control (node host proxy)
2026-01-15 05:30:02 +00:00
2026-01-27 03:23:42 +00:00
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).
2026-01-15 05:30:02 +00:00
2026-01-27 03:23:42 +00:00
Use `gateway.nodes.browser.mode` to control auto-routing and `gateway.nodes.browser.node` to pin a specific node if multiple are connected.
2026-01-15 05:30:02 +00:00
2026-01-27 03:23:42 +00:00
Security + remote setup: [Browser tool ](/tools/browser ), [Remote access ](/gateway/remote ), [Tailscale ](/gateway/tailscale ), [Security ](/gateway/security )