OpenClaw Browser Relay Chrome extension not working.
I’m having trouble getting the OpenClaw Browser Relay to work via the Chrome extension.
• Environment: macOS, OpenClaw 2026.2.19-2, Gateway running locally on 127.0.0.1:18789
• Extension shows: Relay reachable and authenticated at http://127.0.0.1:18789/
• However, any browser tool call fails with an error along the lines of:Chrome extension relay is running, but no tab is connected. Click the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").
What I’ve already tried:
• Removed duplicate OpenClaw Browser Relay extensions from Chrome so only one is active.
• Verified port and token match the gateway config (OPENCLAW_GATEWAY_TOKEN, port 18789).
• Clicked the extension icon on an active tab and tried to attach it.
• Restarted the OpenClaw gateway and Chrome multiple times.
Despite this, the browser tool still can’t attach to the tab (and I’ve also seen invalid handshake / policy violation (1008) in the logs when the relay tries to talk to the gateway).
Looking for guidance on:
• How to properly verify that a tab is actually “attached” from the gateway’s perspective, and
• Whether there’s any additional config needed for the extension relay beyond token + port.
• Environment: macOS, OpenClaw 2026.2.19-2, Gateway running locally on 127.0.0.1:18789
• Extension shows: Relay reachable and authenticated at http://127.0.0.1:18789/
• However, any browser tool call fails with an error along the lines of:Chrome extension relay is running, but no tab is connected. Click the OpenClaw Chrome extension icon on a tab to attach it (profile "chrome").
What I’ve already tried:
• Removed duplicate OpenClaw Browser Relay extensions from Chrome so only one is active.
• Verified port and token match the gateway config (OPENCLAW_GATEWAY_TOKEN, port 18789).
• Clicked the extension icon on an active tab and tried to attach it.
• Restarted the OpenClaw gateway and Chrome multiple times.
Despite this, the browser tool still can’t attach to the tab (and I’ve also seen invalid handshake / policy violation (1008) in the logs when the relay tries to talk to the gateway).
Looking for guidance on:
• How to properly verify that a tab is actually “attached” from the gateway’s perspective, and
• Whether there’s any additional config needed for the extension relay beyond token + port.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
