OpenClaw merged PR #120390, "fix(browser): harden extension relay authorization", a P1 security-boundary fix for the Chrome extension relay.
The extension relay is powerful by design. It lets OpenClaw operate against browser tabs through a controlled connection, which means authorization has to stay current at the browser edge. This PR closes gaps around pairing secrets, WebSocket URL safety, and tab-group membership checks.
What Changed
The relay still advertises only grouped tabs, but the extension now rechecks OpenClaw tab-group membership before authority-bearing commands. That includes attach, Chrome DevTools Protocol operations, close, and activate flows.
That extra check matters because relay state can become stale. If a user removes a tab from the OpenClaw group, old relay knowledge should not preserve access to that tab. The browser edge is now responsible for confirming current membership before taking action.
Pairing rules are tighter as well. The extension now accepts only the CLI's canonical 64-character lowercase hex secret format. Plain WebSocket pairing is limited to loopback, while remote pairing requires TLS. Embedded URL credentials, unknown or duplicate query parameters, and unsafe gateway hints are rejected.
Why Operators Should Care
Browser automation is one of the most sensitive parts of an agent runtime. A browser tab may contain authenticated web apps, private documents, dashboards, email, or admin consoles. It is not enough for the relay to be convenient; its authority needs to shrink when user intent changes.
PR #120390 improves that trust model in two ways. First, it makes pairing harder to spoof or weaken through malformed connection details. Second, it makes tab authorization depend on live browser grouping rather than stale relay memory.
The release notes also mention documentation for authenticated external CDP clients, including same-host and direct remote topologies. That gives operators a clearer model for when remote browser control is acceptable and what transport protections are expected.
Validation
The PR reports 48 focused unit tests, seven real Chromium extension end-to-end tests, and a full browser plugin suite with 2,244 passing tests and one skip. It also passed formatting, lint, typecheck, boundary, dead-code, cycle, and guard checks.
Documentation validation checked 6,508 links with zero broken links, and the final autoreview was clean.
Bottom Line
OpenClaw's browser relay is useful because it gives agents a practical bridge into real web workflows. That usefulness depends on crisp authorization boundaries.
PR #120390 makes those boundaries more explicit: current tab-group membership gates sensitive commands, pairing secrets must match the canonical shape, and remote relay connections require safer WebSocket handling. For anyone using OpenClaw's browser extension in a real workspace, this is a meaningful security hardening patch.