Browser Relay disconnect workaround: fall back to openclaw managed profile first
Scenario: Chrome Relay shows ON then disconnects after interaction. Triage by isolating extension path vs managed profile, then pin config to a stable profile before deeper relay debugging.
REDDITDiscovered 2026-02-14Author u/michalsadowski
Prerequisites
- OpenClaw gateway runs on the same machine as Chrome relay extension (or has node proxy to that machine).
- Extension is installed and can be toggled ON at least once.
Steps
- Check managed browser path first: start openclaw profile and run snapshot to confirm core browser tooling is healthy.
- If managed profile is stable, set browser.defaultProfile=openclaw temporarily to keep automation available.
- Then test relay path separately: re-attach extension tab, run tabs/snapshot, and observe whether disconnect occurs only on interaction.
- Collect error/request traces before filing issue, including OS, Chrome version, and gateway build.
Commands
openclaw browser --browser-profile openclaw startopenclaw browser --browser-profile openclaw snapshot --interactiveopenclaw config set browser.defaultProfile "openclaw"openclaw gateway restartVerify
Automation remains stable on openclaw profile; relay-specific disconnect can be reproduced independently with diagnostics attached.
Caveats
- This is a mitigation path, not a root-cause fix for extension relay regressions.
- If session is sandboxed, host browser control may be blocked unless allowHostControl is enabled（需验证）.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗