relay-fallback-browser

Route browser tasks to Chrome Relay with automatic fallback to headless browsing.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/AIDEN0602/openclaw --skill relay-fallback-browser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relay-fallback-browser
Source: https://github.com/AIDEN0602/openclaw/tree/main/skills/relay-fallback-browser
Command: npx skills add https://github.com/AIDEN0602/openclaw --skill relay-fallback-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browsers and automation often rely on a Chrome Relay connection; when the relay becomes unavailable or unreliable, users are left without a working browsing path. This skill defines a robust policy to automatically fall back to a managed headless browser or a free-search path without requiring manual user toggles, ensuring continuity of actions like browsing, screenshots, and data extraction.

Core Features & Use Cases

  • Primary path: Chrome Relay for user-facing browsing to preserve the user footprint and compatibility.
  • Fallback path: If relay is disconnected, automatically switch to a managed headless browser or free-search to complete tasks without user intervention.
  • Recovery handling: Includes a recovery hook to self-heal and retry when the browser service becomes unhealthy.

Quick Start

Start the jarvis browser path and let the system switch to the fallback path automatically if relay fails.

Frequently Asked Questions about relay-fallback-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep browser automation running when Chrome Relay disconnects?

Browser automation continuity is maintained by an execution policy that checks relay status and automatically routes tasks to a managed headless browser or free-search when relay becomes unavailable, requiring no manual user toggles.

What is automatic fallback routing for web browsing tasks?

Automatic fallback routing is an execution policy that prefers Chrome Relay for user-facing browsing, then seamlessly switches to a managed headless browser or free-search path if the relay gateway becomes unhealthy or disconnected.

How does headless browser fallback handle screenshot capture and data extraction?

Screenshot capture and web data extraction fallback works by detecting an unreliable relay connection and automatically rerouting those specific browsing actions to a managed headless browser to ensure task completion without interruption.

Can I recover browser automation tasks after a relay gateway service becomes unhealthy?

Unhealthy relay gateway recovery is handled by a built-in recovery hook that self-heals and retries the browser service, allowing web browsing and data extraction tasks to resume on the primary relay path automatically.

Does browser fallback routing require manual toggles when switching to headless mode?

Browser fallback routing requires no manual toggles; the execution policy automatically detects relay unavailability and switches to a managed headless browser or free-search path to complete web browsing actions transparently.

What are the limitations of relay-first browsing with automatic fallback?

Relay-first browsing fallback relies on a managed headless browser or free-search as secondary paths, meaning tasks complete but may lose the user-facing footprint and compatibility preserved by the primary Chrome Relay connection.