#Browser access since update
1 messages · Page 1 of 1 (latest)
First, can you paste openclaw --version?
If sandbox is really off, allowHostControl is probably not the missing piece. That setting only matters for sandboxed sessions.
What I’d check first after this update:
-
Browser plugin got excluded
If you useplugins.allow, make sure it includes"browser", not just"telegram". -
Tool policy blocks it
If you usetools.allow, make sure"browser"is in there too.tools.allowstill applies even when sandboxing is off. -
Local CDP attach is being SSRF-blocked
If the tool exists but cannot attach, use:attachOnly: truecdpUrl: "http://127.0.0.1:9222"- if you have a restrictive
browser.ssrfPolicy, allow both127.0.0.1andlocalhostin bothallowedHostnamesandhostnameAllowlist
Quick checks:
openclaw --version
openclaw browser status
openclaw browser profiles
openclaw status --all
Useful docs:
- https://docs.openclaw.ai/tools/browser
- https://docs.openclaw.ai/gateway/troubleshooting
- https://docs.openclaw.ai/gateway/configuration-reference
- https://docs.openclaw.ai/gateway/sandboxing
If you paste:
openclaw --version