Bug type

Behavior bug (incorrect output/state without crash)

Summary

Chrome Extension Relay frequently disconnects or disables itself, requiring manual user intervention to restore functionality.

Steps to reproduce

Steps to reproduce
1. Launch OpenClaw with Chrome Extension Relay enabled.
2. Use the browser tool normally (attach tab, interact via relay).
3. Continue working for a period of time (normal workflow).
4. Observe relay disconnect or disabled state.
5. Agent prompts user to manually re-enable the relay.

Expected behavior

Relay connection remains stable, or automatically detects disconnection and self-recovers without user involvement.

Actual behavior

Relay drops communication or becomes disabled.
Agent repeatedly prompts user to re-enable the extension manually.
No built-in recovery or auto-heal mechanism is triggered.

OpenClaw version

2026.3.1

Operating system

macOS 15.x (Apple Silicon)

Install method

CLI install (Homebrew + npm global) running gateway locally

Logs, screenshots, and evidence

Observed behavior:
	•	Relay becomes unreachable despite Chrome running.
	•	Agent prompts user to enable extension.
	•	Manual intervention via Chrome extensions panel restores functionality.

Temporary macOS workaround implemented using Peekaboo automation:
https://clawhub.ai/i-am-rad/chrome-extension-relay-helper-mac

This helper programmatically enables the relay and restores operation, confirming the issue is recoverable via automation.

Impact and severity

Affected: All users relying on Chrome Extension Relay
Severity: Medium (workflow interruption and repeated friction)
Frequency: Frequent / recurring during normal use
Consequence:
• Agents cannot proceed autonomously
• Repeated manual relay reactivation
• Additional context usage from custom helper skills
• Degraded perception of automation reliability

Additional information

This is effectively a missing self-heal mechanism.

Recommended fix:
• Add relay healthcheck (CDP reachability, tab attachment, extension state).
• Implement reconnect pipeline with exponential backoff.
• Add optional browser.relay.autoHeal config flag (default off).
• Include retry limits and cooldown safeguards.

Temporary workaround exists (Peekaboo-based automation on macOS), but this should be integrated into core to eliminate custom skill overhead and repeated user prompts.