let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #895 from mukhtharcm/feat/chrome-browser-improvements

Browse Source 
feat(browser): add support for authenticated remote browser profiles
This commit is contained in:
Peter Steinberger
2026-01-16 08:32:02 +00:00
committed by GitHub
parent 2dae4d382f bf15c87d2b
commit 3b1b14b0b1
15 changed files with 207 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tools/browser.md
View File

@@ -154,6 +154,14 @@ Example:
Use `profiles.<name>.cdpUrl` for **remote CDP** if you want the Gateway to talk
directly to a Chromium-based browser instance without a remote control server.
Remote CDP URLs can include auth:
- Query tokens (e.g., `https://provider.example?token=<token>`)
- HTTP Basic auth (e.g., `https://user:pass@provider.example`)
Clawdbot preserves the auth when calling `/json/*` endpoints and when connecting
to the CDP WebSocket. Prefer environment variables or secrets managers for
tokens instead of committing them to config files.
### Running the control server on the browser machine
Run a standalone browser control server (recommended when your Gateway is remote):