diff --git a/docs/tools/browser.md b/docs/tools/browser.md
index ca04ca5ec..d740b9b61 100644
--- a/docs/tools/browser.md
+++ b/docs/tools/browser.md
@@ -212,6 +212,10 @@ OpenClaw can also drive **your existing Chrome tabs** (no separate “openclaw
 
 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:
 - The Gateway runs locally (same machine) or a node host runs on the browser machine.
 - A local **relay server** listens at a loopback `cdpUrl` (default: `http://127.0.0.1:18792`).
diff --git a/docs/tools/chrome-extension.md b/docs/tools/chrome-extension.md
index 47494c3dd..4f1e57073 100644
--- a/docs/tools/chrome-extension.md
+++ b/docs/tools/chrome-extension.md
@@ -12,6 +12,18 @@ The OpenClaw 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: