From 2bd91a0f02b4a526e5db4241bc70859985f5f7ba Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sat, 4 Apr 2026 20:29:31 +0100 Subject: [PATCH] docs: refresh browser existing-session mirror refs --- docs/gateway/configuration-reference.md | 4 ++++ docs/gateway/doctor.md | 5 +++++ docs/tools/browser-linux-troubleshooting.md | 4 ++++ .../tools/browser-wsl2-windows-remote-cdp-troubleshooting.md | 2 ++ 4 files changed, 15 insertions(+) diff --git a/docs/gateway/configuration-reference.md b/docs/gateway/configuration-reference.md index 20b921331e4..e398227107a 100644 --- a/docs/gateway/configuration-reference.md +++ b/docs/gateway/configuration-reference.md @@ -2628,6 +2628,10 @@ See [Plugins](/tools/plugin). - `existing-session` profiles are host-only and use Chrome MCP instead of CDP. - `existing-session` profiles can set `userDataDir` to target a specific Chromium-based browser profile such as Brave or Edge. +- `existing-session` profiles keep the current Chrome MCP route limits: + snapshot/ref-driven actions instead of CSS-selector targeting, one-file upload + hooks, no dialog timeout overrides, no `wait --load networkidle`, and no + `responsebody`, PDF export, download interception, or batch actions. - Local managed `openclaw` profiles auto-assign `cdpPort` and `cdpUrl`; only set `cdpUrl` explicitly for remote CDP. - Auto-detect order: default browser if Chromium-based → Chrome → Brave → Edge → Chromium → Chrome Canary. diff --git a/docs/gateway/doctor.md b/docs/gateway/doctor.md index 611efd1e85a..c30c198d66f 100644 --- a/docs/gateway/doctor.md +++ b/docs/gateway/doctor.md @@ -194,6 +194,11 @@ still requires: - remote debugging enabled in that browser - approving the first attach consent prompt in the browser +Readiness here is only about local attach prerequisites. Existing-session keeps +the current Chrome MCP route limits; advanced routes like `responsebody`, PDF +export, download interception, and batch actions still require a managed +browser or raw CDP profile. + This check does **not** apply to Docker, sandbox, remote-browser, or other headless flows. Those continue to use raw CDP. diff --git a/docs/tools/browser-linux-troubleshooting.md b/docs/tools/browser-linux-troubleshooting.md index 902dae98048..09abab1d586 100644 --- a/docs/tools/browser-linux-troubleshooting.md +++ b/docs/tools/browser-linux-troubleshooting.md @@ -135,6 +135,10 @@ Fix options: Notes: - `user` is host-only. For Linux servers, containers, or remote hosts, prefer CDP profiles. +- `user` / other `existing-session` profiles keep the current Chrome MCP limits: + ref-driven actions, one-file upload hooks, no dialog timeout overrides, no + `wait --load networkidle`, and no `responsebody`, PDF export, download + interception, or batch actions. - Local `openclaw` profiles auto-assign `cdpPort`/`cdpUrl`; only set those for remote CDP. - Remote CDP profiles accept `http://`, `https://`, `ws://`, and `wss://`. Use HTTP(S) for `/json/version` discovery, or WS(S) when your browser diff --git a/docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md b/docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md index 7af077b6cf3..695e35ca177 100644 --- a/docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md +++ b/docs/tools/browser-wsl2-windows-remote-cdp-troubleshooting.md @@ -40,6 +40,8 @@ Choose this when: - OpenClaw and Chrome are on the same machine - you want the local signed-in browser state - you do not need cross-host browser transport +- you do not need advanced managed/raw-CDP-only routes like `responsebody`, PDF + export, download interception, or batch actions For WSL2 Gateway + Windows Chrome, prefer raw remote CDP. Chrome MCP is host-local, not a WSL2-to-Windows bridge.