From fe98557ed255187200f5d05cd38f8a3b9c7c2d63 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 25 Apr 2026 12:58:50 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@9b1dd9e5738d547a97fa66d4b0741f6d6ead46e1 --- .openclaw-sync/source.json | 4 ++-- docs/tools/browser.md | 22 ++++++++++++++++++++++ 2 files changed, 24 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 1120ebbd4..d415a86a2 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "ab1d1a5c9eb60d24b1e90ca3b844b1c5d31b815e", - "syncedAt": "2026-04-25T12:47:35.260Z" + "sha": "9b1dd9e5738d547a97fa66d4b0741f6d6ead46e1", + "syncedAt": "2026-04-25T12:57:29.148Z" } diff --git a/docs/tools/browser.md b/docs/tools/browser.md index e094b246b..cb4471e1c 100644 --- a/docs/tools/browser.md +++ b/docs/tools/browser.md @@ -547,6 +547,28 @@ Notes: browser node. If Chrome lives elsewhere and no browser node is connected, use remote CDP or a node host instead. +### Custom Chrome MCP launch + +Override the spawned Chrome DevTools MCP server per profile when the default +`npx chrome-devtools-mcp@latest` flow is not what you want (offline hosts, +pinned versions, vendored binaries): + +| Field | What it does | +| ------------ | -------------------------------------------------------------------------------------------------------------------------- | +| `mcpCommand` | Executable to spawn instead of `npx`. Resolved as-is; absolute paths are honored. | +| `mcpArgs` | Argument array passed verbatim to `mcpCommand`. Replaces the default `chrome-devtools-mcp@latest --autoConnect` arguments. | + +When `cdpUrl` is set on an existing-session profile, OpenClaw skips +`--autoConnect` and forwards the endpoint to Chrome MCP automatically: + +- `http(s)://...` → `--browserUrl ` (DevTools HTTP discovery endpoint). +- `ws(s)://...` → `--wsEndpoint ` (direct CDP WebSocket). + +Endpoint flags and `userDataDir` cannot be combined: when `cdpUrl` is set, +`userDataDir` is ignored for Chrome MCP launch, since Chrome MCP attaches to +the running browser behind the endpoint rather than opening a profile +directory. + Compared to the managed `openclaw` profile, existing-session drivers are more constrained: