OpenClaw Browser Control Bug Report

Issue Summary

Browser automation is broken in OpenClaw 2026.2.9 (and earlier versions). Both Chrome extension relay and OpenClaw-managed browser profiles fail to maintain stable control connections.

Environment

• OpenClaw Version: 2026.2.9
• OS: Windows 10 Pro (Build 19045)
• Browser: Chrome (latest), Chrome extension installed
• Gateway: Running via npm

Problem Description

1. Chrome Extension Relay (profile="chrome")

• Expected: Take control of existing Chrome tabs via OpenClaw extension
• Actual:
  • Requires manual connection (click extension icon on each tab)
  • Connection drops frequently (every few commands)
  • Returns error: "Chrome extension relay is running, but no tab is connected"
  • Gateway keeps switching to this profile even when using OpenClaw-managed browser

2. OpenClaw-Managed Browser (profile="openclaw")

• Expected: Isolated browser instance with full control
• Actual:
  • Opens URLs successfully
  • Creates tabs successfully
  • FAILS on all interaction operations: snapshot, screenshot, click, type, act
  • Returns same "no tab connected" error
  • Gateway appears to default to chrome profile internally

Reproduction Steps

1. Run openclaw gateway (or any gateway command)
2. Use browser(action="open", profile="openclaw", targetUrl="https://youtube.com")
3. URL opens in new browser window
4. Attempt browser(action="snapshot", targetId="[tab-id]")
5. Result: Error - "Chrome extension relay is running, but no tab is connected"

Error Messages

- "Chrome extension relay is running, but no tab is connected. Click the OpenClaw Chrome extension icon on a tab to attach it (profile \"chrome\")."
- "Can't reach the OpenClaw browser control service"
- "Error: tab not found"

Impact

• Critical: Browser automation completely non-functional
• Cannot automate: clicking, typing, form filling, screenshots, snapshots
• Can only open URLs (limited functionality)

Workarounds Tried

1. Restart OpenClaw gateway multiple times - no effect
2. Close all Chrome processes and restart with remote debugging port - no effect
3. Use OpenClaw-managed browser - opens URLs but cannot interact
4. Reinstall Chrome extension - not yet tried (may fix)

Expected Behavior

Either:

1. Chrome extension relay should maintain stable connections
2. OpenClaw-managed browser should fully work (open + interact)
3. Profile switching should work correctly

Severity

CRITICAL - Browser automation is a core feature of OpenClaw

Reported by: Shahir (OpenClaw user)
Date: 2026-02-11
Version: 2026.2.9