let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify extension tab attachment

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-15 05:20:56 +00:00
parent 139f80a291
commit 1fe8df85cb
3 changed files with 18 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/start/faq.md
View File

@@ -414,6 +414,7 @@ Then Chrome → `chrome://extensions` → enable “Developer mode” → “Loa
Full guide (including remote Gateway via Tailscale + security notes): [Chrome extension](/tools/chrome-extension) Full guide (including remote Gateway via Tailscale + security notes): [Chrome extension](/tools/chrome-extension)
If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need `clawdbot browser serve`. If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need `clawdbot browser serve`.
You still need to click the extension button on the tab you want to control (it doesn’t auto-attach).
## Sandboxing and memory ## Sandboxing and memory

2
docs/tools/browser.md
View File

@@ -218,7 +218,7 @@ Full guide: [Chrome extension](/tools/chrome-extension)
Flow: Flow:
- You run a **browser control server** (Gateway on the same machine, or `clawdbot browser serve`). - You run a **browser control server** (Gateway on the same machine, or `clawdbot browser serve`).
- A local **relay server** listens at a loopback `cdpUrl` (default: `http://127.0.0.1:18792`). - A local **relay server** listens at a loopback `cdpUrl` (default: `http://127.0.0.1:18792`).
- You click the **Clawdbot Browser Relay** extension icon on a tab to attach. - You click the **Clawdbot Browser Relay** extension icon on a tab to attach (it does not auto-attach).
- The agent controls that tab via the normal `browser` tool, by selecting the right profile. - The agent controls that tab via the normal `browser` tool, by selecting the right profile.
If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need `clawdbot browser serve`. If the Gateway runs on the same machine as Chrome (default setup), you usually **do not** need `clawdbot browser serve`.

16
docs/tools/chrome-extension.md
View File

@@ -70,6 +70,22 @@ Then target it:
- Badge shows `ON` when attached. - Badge shows `ON` when attached.
- Click again to detach. - Click again to detach.
## Which tab does it control?
- It does **not** automatically control “whatever tab you’re looking at”.
- It controls **only the tab(s) you explicitly attached** by clicking the toolbar button.
- To switch: open the other tab and click the extension icon there.
## Badge + common errors
- `ON`: attached; Clawdbot can drive that tab.
- `…`: connecting to the local relay.
- `!`: relay not reachable (most common: browser relay server isn’t running on this machine).
If you see `!`:
- Make sure the Gateway is running locally (default setup), or run `clawdbot browser serve` on this machine (remote gateway setup).
- Open the extension Options page; it shows whether the relay is reachable.
## Do I need `clawdbot browser serve`? ## Do I need `clawdbot browser serve`?
### Local Gateway (same machine as Chrome) — usually **no** ### Local Gateway (same machine as Chrome) — usually **no**