vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 10:40:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

browser: route existing-session user profile through browser nodes (#68891)

Browse Source 
* browser: route user profile through browser nodes

* browser: align existing-session node docs

* browser: preserve host fallback on node discovery errors

* browser: preserve configured node pin errors

* browser: widen config mock in node pin test
This commit is contained in:
Mariano
2026-04-19 12:21:23 +02:00
committed by GitHub
parent d83215084f
commit 8cb73844c8
8 changed files with 150 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/gateway/configuration-reference.md
View File

@@ -2967,7 +2967,8 @@ See [Plugins](/tools/plugin).
- `profiles.*.cdpUrl` accepts `http://`, `https://`, `ws://`, and `wss://`.
Use HTTP(S) when you want OpenClaw to discover `/json/version`; use WS(S)
when your provider gives you a direct DevTools WebSocket URL.
- `existing-session` profiles are host-only and use Chrome MCP instead of CDP.
- `existing-session` profiles use Chrome MCP instead of CDP and can attach on
the selected host or through a connected browser node.
- `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:

2
docs/help/faq.md
View File

@@ -1258,7 +1258,7 @@ for usage/billing and raise limits as needed.
openclaw browser --browser-profile chrome-live tabs
```
This path is host-local. If the Gateway runs elsewhere, either run a node host on the browser machine or use remote CDP instead.
This path can use the local host browser or a connected browser node. If the Gateway runs elsewhere, either run a node host on the browser machine or use remote CDP instead.
Current limits on `existing-session` / `user`:

5
docs/tools/browser.md
View File

@@ -532,8 +532,9 @@ Notes:
- Existing-session dialog hooks do not support timeout overrides.
- Some features still require the managed browser path, including batch
actions, PDF export, download interception, and `responsebody`.
- Existing-session is host-local. If Chrome lives on a different machine or a
different network namespace, use remote CDP or a node host instead.
- Existing-session can attach on the selected host or through a connected
browser node. If Chrome lives elsewhere and no browser node is connected, use
remote CDP or a node host instead.
## Isolation guarantees