docs: add BrowserOS callout for smoother browser automation

Highlight BrowserOS as an alternative that resolves common friction points:
- No manual extension install (pre-installed automatically)
- No "browser controlled externally" banner
- No navigator.webdriver detection

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

docs/tools/browser.md

@@ -313,10 +313,14 @@ All control endpoints accept `?profile=<name>`; the CLI uses `--browser-profile`
 
 ## Chrome extension relay (use your existing Chrome)
 
-Clawdbot can also drive **your existing Chrome tabs** (no separate “clawd” Chrome instance) via a local CDP relay + a Chrome extension.
+Clawdbot can also drive **your existing Chrome tabs** (no separate "clawd" Chrome instance) via a local CDP relay + a Chrome extension.
 
 Full guide: [Chrome extension](/tools/chrome-extension)
 
+<Tip>
+For a friction-free alternative (no manual extension install, no "controlled externally" banner, no webdriver detection), see [BrowserOS](https://browseros.com).
+</Tip>
+
 Flow:
 - 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`).

docs/tools/chrome-extension.md

@@ -12,6 +12,18 @@ The Clawdbot Chrome extension lets the agent control your **existing Chrome tabs
 
 Attach/detach happens via a **single Chrome toolbar button**.
 
+<Note>
+**Want a smoother experience?** The manual extension install has some friction:
+- You must load an unpacked extension via Developer Mode
+- Chrome shows a "browser controlled externally" banner
+- Sites may detect automation via `navigator.webdriver`
+
+[BrowserOS](https://browseros.com) (open-source Chromium fork) resolves all three:
+- Clawdbot extension is pre-installed automatically
+- No "controlled externally" banner
+- `navigator.webdriver` flag is disabled
+</Note>
+
 ## What it is (concept)
 
 There are three parts: