# Fix OpenClaw Browser Extension: Relay Not Working

Learn how to fix OpenClaw browser extension relay not working by checking Gateway status, attached tabs, extension permissions, browser profile, and relay access.

## What Does "OpenClaw Browser Extension: Relay Not Working" Mean?

"OpenClaw Browser Extension: Relay Not Working" means the browser extension cannot properly connect your active browser tab with OpenClaw.

The extension works like a bridge between your browser and OpenClaw. When the relay fails, OpenClaw may not be able to read the page, control the tab, click buttons, fill forms, or continue browser-based tasks.

This usually happens when:

- OpenClaw Gateway is not running
- The relay service is not reachable
- The browser tab is not attached
- The extension is disabled or missing permissions
- The wrong browser profile is being used
- VPN, firewall, or localhost settings are blocking the connection
- The browser session became stale after sleep, restart, or update

## Quick Fix Checklist

| Check | How |
|-------|-----|
| Is OpenClaw Gateway running? | Check the local Gateway status |
| Can you open the Control UI? | Try opening http://127.0.0.1:18789 |
| Is the browser extension enabled? | Check chrome://extensions |
| Is the correct tab attached? | Open target page, click extension icon |
| Is the correct browser profile being used? | Make sure OpenClaw is controlling the expected profile |
| Is VPN/firewall blocking localhost? | Temporarily test without VPN or strict security tools |
| Is the browser stale after sleep/restart? | Restart Gateway and reload the tab |

## Fix 1: Restart and Verify the OpenClaw Gateway

The browser extension needs the Gateway to communicate with OpenClaw. If the Gateway is down or stale, the extension relay can fail.

```bash
openclaw gateway status
openclaw gateway restart
```

If restart does not work:

```bash
openclaw gateway start
```

Then test:

```bash
curl http://127.0.0.1:18789
```

## Fix 2: Reattach the Current Browser Tab

Sometimes the relay is available but no active browser tab is attached.

1. Open the website you want OpenClaw to control
2. Click the OpenClaw Browser Relay extension icon
3. Attach the current tab
4. Reload the page
5. Retry the browser action inside OpenClaw

## Fix 3: Check Extension Status and Permissions

1. Open `chrome://extensions`
2. Find the OpenClaw Browser Relay extension
3. Make sure it is enabled
4. Open Details
5. Check site access
6. Allow access for the website you want to automate
7. Reload the tab
8. Click the extension icon again

Browser extensions may not work on pages like `chrome://settings`, `chrome://extensions`, or `chrome://flags`.

## Fix 4: Use the Correct Browser Profile

OpenClaw may use a separate browser profile called `openclaw`. This profile is different from your normal Chrome profile.

```bash
openclaw browser start
openclaw browser open https://example.com
openclaw browser tabs
```

For logged-in websites, sign in manually inside the OpenClaw browser profile instead of giving credentials to the model.

## Fix 5: Test Browser Control From CLI

```bash
openclaw browser status
openclaw browser tabs
openclaw browser screenshot
```

| Result | Meaning |
|--------|---------|
| `browser status` fails | Browser service or Gateway issue |
| `tabs` shows no target tab | Tab is not attached or wrong profile |
| `screenshot` fails | Browser control is not connected |
| CLI works but extension fails | Extension permission or attachment issue |

## Fix 6: Check Localhost, Port, VPN, and Firewall Issues

The extension may fail if local browser traffic cannot reach OpenClaw's local Gateway.

- Can you open `http://127.0.0.1:18789`?
- Is another app using port 18789?
- Is VPN blocking localhost traffic?
- Is firewall/security software blocking local connections?

```bash
lsof -i :18789
curl http://127.0.0.1:18789
```

Do not expose browser control ports publicly.

## Fix 7: Fix Linux Chromium or Snap Browser Problems

Snap's AppArmor confinement can interfere with how OpenClaw spawns and monitors the browser process.

Fix options:

- Use Google Chrome instead of Snap Chromium
- Use Brave or Edge if available
- Use a non-snap Chromium build
- Use attach-only mode when needed

```json
{
  "browser": {
    "enabled": true,
    "attachOnly": true,
    "headless": true,
    "noSandbox": true
  }
}
```

## Fix 8: Clear Stale Browser State

The relay can fail after laptop sleep, browser restart, Chrome update, Gateway restart, or extension update.

1. Close the target tab
2. Restart Gateway
3. Reopen the target website
4. Click the extension icon
5. Attach the tab again
6. Retry the workflow

## Fix 9: Update OpenClaw and Reload the Extension

```bash
openclaw --version
openclaw update
```

Reload the extension at `chrome://extensions`, then restart:

```bash
openclaw gateway restart
```

## Common Scenarios and Solutions

### Scenario 1: Extension Is Installed but Nothing Happens
Cause: Extension disabled, site access blocked, wrong profile, no tab attached.
Fix: Enable extension, allow site access, reattach current tab.

### Scenario 2: Relay Worked Before, Then Stopped
Cause: Gateway restarted, browser slept, Chrome updated, extension permission reset.
Fix: Restart Gateway, reload tab, reattach extension, confirm dashboard opens.

### Scenario 3: Gateway Works but Extension Still Fails
Cause: Browser cache, stale tab, wrong profile, extension state issue.
Fix: Open `http://127.0.0.1:18789` directly, restart browser, reattach tab, reload extension.

### Scenario 4: Browser Opens but Agent Cannot Control It
Cause: Wrong browser profile, browser control not enabled, sandbox restrictions.
Fix: Use `openclaw browser tabs`, use the openclaw profile, enable host browser control only when needed.

### Scenario 5: Linux Browser Relay Fails
Cause: Snap Chromium, AppArmor confinement, sandbox/browser spawn issue.
Fix: Use Chrome, Brave, Edge, or non-snap Chromium. Use attach-only mode.

## When to Stop Using the Extension Relay

Use the extension relay when:
- You need OpenClaw to use your current browser tab
- You need an already logged-in browser session
- You are actively supervising the task

Use managed OpenClaw when:
- You want repeatable workflows
- You want fewer local browser issues
- You run scheduled tasks
- You do not want workflows to stop when your laptop sleeps

## Easier Option: Run OpenClaw on Ampere.sh

Local browser relay issues usually come from Gateway restarts, browser profiles, extension permissions, localhost access, stale tabs, and machine sleep. If you want to run OpenClaw workflows without managing local setup, managed hosting is the cleaner path.

[Run OpenClaw on Ampere.sh](https://www.ampere.sh/setup)

## Final Checklist Before You Retry

- Gateway is running
- `http://127.0.0.1:18789` opens
- Extension is enabled
- Site access is allowed
- Current tab is attached
- Correct browser profile is selected
- VPN/firewall is not blocking localhost
- Browser CLI can see tabs
- OpenClaw is updated
- Extension is reloaded
- Linux users are not stuck on Snap Chromium issues

## FAQs

**Why is my OpenClaw Browser Extension relay not working?**
It usually means the browser extension cannot connect your active browser tab to OpenClaw. This can happen if the Gateway is not running, the tab is not attached, the relay is unreachable, or the extension does not have permission to access the page.

**Why does OpenClaw say no tab is connected?**
This means the relay may be running, but OpenClaw has not attached to your current browser tab. Open the page you want OpenClaw to use, then click the OpenClaw Browser Extension icon to connect that tab.

**Does OpenClaw Browser Extension need the Gateway running?**
Yes. The extension needs OpenClaw Gateway or the local browser control service to be running.

**Can VPN or firewall cause OpenClaw relay issues?**
Yes. VPNs, firewalls, antivirus tools, or strict browser security settings can block local connections.

**Does OpenClaw use my normal Chrome profile?**
Not always. OpenClaw may use a separate browser profile for automation.

**What is the easiest way to avoid OpenClaw browser relay problems?**
Use a stable OpenClaw setup with managed hosting or a dedicated browser environment.