Using the Chrome Browser Relay with OpenClaw Running on a Remote VPS

A common question from the OpenClaw Discord: "My OpenClaw is on a VPS but my Chrome browser is on my Mac — how do I use the Browser Relay extension?"

This setup is totally possible, but requires one extra piece: a Node running on your local Mac that bridges your Chrome to the remote Gateway.

The Problem

The Browser Relay extension needs to talk to the relay server at http://127.0.0.1:18792 by default. If your Gateway is on a VPS, there is no local relay server — hence the ! badge error.

The Solution: Run a Node on Your Mac

OpenClaw Nodes let you extend your agent's reach to other machines. When a Node runs locally, it hosts the relay server your Chrome extension needs.

Step 1: Install OpenClaw on Your Mac

Even though your main Gateway is on the VPS, you need the OpenClaw CLI locally:

curl -fsSL https://clawd.bot/install.sh | bash

Step 2: Pair Your Mac as a Node

On your Mac:

openclaw pair --gateway https://your-vps-gateway:18888

Follow the prompts to complete pairing. Your VPS Gateway will now recognize your Mac as a connected node.

Step 3: Install the Browser Relay Extension

On your Mac:

openclaw browser extension install

This creates the extension files. Get the path:

openclaw browser extension path

Step 4: Load the Extension in Chrome

1. Go to chrome://extensions
2. Enable Developer mode (top right)
3. Click Load unpacked → select the folder from openclaw browser extension path
4. Pin the extension to your toolbar

Step 5: Attach a Tab

1. Open any tab you want your agent to control
2. Click the Browser Relay extension icon
3. The badge should show ON (not ! or ...)

Step 6: Use It in OpenClaw

Now from your VPS-hosted agent, use the chrome browser profile:

Or when prompting your agent: "Use my Chrome browser to check Gmail" — it will route through your Mac node automatically.

Troubleshooting

Badge shows !: The relay server isn't reachable. Make sure your Node is running (openclaw gateway status on your Mac shows it connected).

Badge shows ...: The extension is connecting. Wait a moment, then click again.

Node not connecting: Check your VPS firewall allows WebSocket connections on the Gateway port.

Why This Works

Your Mac Node maintains a persistent connection to your VPS Gateway. When your agent requests browser actions, they're routed to the Node, which executes them against your local Chrome via the relay server. The extension badge confirms the tab is attached and ready.

Based on a question from the OpenClaw Discord #help forum. Full docs: docs.openclaw.ai/tools/chrome-extension