OpenClaw Browser Relay for Chrome

OpenClaw Browser Relay

Attach OpenClaw to your existing Chrome tab via a local CDP relay server.

This extension enables OpenClaw to control your current Chrome tab via a secure local CDP relay, unlocking advanced browser automation features like clicking, typing, navigation, and form interaction, directly from your AI assistant.

Personalized by PAIO This version of the relay tool is Powered by PAIO. While the core functionality remains an unmodified, high-performance bridge for browser control, the interface has been personalized to provide a smoother user experience for the community.

Community-Focused & Unmodified Core As independent developers and users, we recognized that installing the necessary extension for browser control was a hurdle for many, as it isn't officially published in the standard web stores. We have unpacked the relay extension and published it here to allow for simple, one-click installation.

No Functional Changes: Every core relay mechanism is identical to the official OpenClaw internal package.

Security First: All relay operations occur over a local WebSocket (default port 18792).

Privacy: No data is sent externally; the extension only communicates with your local relay server.

Transparency: Users are encouraged to inspect the source code to verify the integrity of the relay.

Getting Started Once installed, simply click the extension icon in your toolbar to attach or detach from a tab. Ensure your local relay server (Gateway) is running to establish a connection.

Attach / detach (toolbar button) • Open the tab you want OpenClaw to control. • Click the extension icon. • Badge shows ON when attached. • Click again to detach. ​ Which tab does it control? • It does not automatically control “whatever tab you’re looking at”. • It controls only the tab(s) you explicitly attached by clicking the toolbar button. • To switch: open the other tab and click the extension icon there. ​ Badge + common errors:

ON: attached; OpenClaw can drive that tab. …: connecting to the local relay. !: relay not reachable (most common: browser relay server isn’t running on this machine).

If you see !:

• Make sure the Gateway is running locally (default setup), or run a node host on this machine if the Gateway runs elsewhere. • Open the extension Options page; it shows whether the relay is reachable. ​ Remote Gateway (use a node host) ​ Local Gateway (same machine as Chrome) — usually no extra steps If the Gateway runs on the same machine as Chrome, it starts the browser control service on loopback and auto-starts the relay server. The extension talks to the local relay; the CLI/tool calls go to the Gateway. ​ Remote Gateway (Gateway runs elsewhere) — run a node host If your Gateway runs on another machine, start a node host on the machine that runs Chrome. The Gateway will proxy browser actions to that node; the extension + relay stay local to the browser machine. If multiple nodes are connected, pin one with gateway.nodes.browser.node or set gateway.nodes.browser.mode.