Stable Browser CDP for Openclaw

A high-stability browser automation layer using Chrome DevTools Protocol to replace unreliable extension-based relays.

jarvis563
v1.0.0
Feb 26, 2026
0
1.1k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install stable-browser

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install stable-browser using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Stable Browser CDP?

Stable Browser is a technical optimization designed to fix common connectivity issues in AI-driven web tasks. By moving away from standard browser extensions which often suffer from WebSocket 403 errors and port confusion, this skill implements a direct Chrome DevTools Protocol (CDP) connection. This ensures a persistent, reliable link between your AI agent and the web browser, enabling seamless automation for complex tasks.

This integration is essential for developers building robust Openclaw Skills that require consistent headless or headed browser control. By utilizing a dedicated profile, it keeps your primary browsing environment clean while providing the agent with a stable, high-performance environment for web interaction.

Stable Browser CDP Use Cases

  • Resolving frequent browser relay disconnections and WebSocket 403 errors during automation.
  • Performing long-running web scraping or data extraction tasks that require stability.
  • Automating social media posting or form filling across persistent user sessions.
  • Running background browser tasks in headless mode for server-side Openclaw Skills.

How Stable Browser CDP Works

  1. The setup script initializes a dedicated Chrome profile located at ~/.chrome-debug-profile.
  2. Chrome is launched with a specific remote debugging port (9222) to enable CDP access.
  3. The skill configures the browser.cdpUrl in the agent environment to establish a direct link.
  4. AI agents execute browser actions using the openclaw profile, bypassing the need for a relay extension.
  5. The system maintains session persistence, allowing the agent to stay logged into required web services.

Stable Browser CDP Setup

To quickly configure the stable browser environment, run the provided setup script:

bash scripts/setup-cdp.sh

This script automates the creation of the debug profile, updates your configuration, and sets up a LaunchAgent on macOS to ensure the browser is available upon login. After installation, ensure you use profile="openclaw" in your browser tool calls.

Stable Browser CDP Data Schema & Taxonomy

The skill manages its environment through an isolated file structure and specific configuration parameters:

Component Path / Identifier Purpose
Profile Directory ~/.chrome-debug-profile Stores isolated cookies, history, and session data.
Config Key browser.cdpUrl The endpoint URL used by the agent to command the browser.
Communication Port 9222 The default local port for the Chrome DevTools Protocol.
Tool Profile openclaw The profile name passed to browser actions to trigger CDP usage.

Stable Browser CDP Advanced Features

  • Support for headless mode via the --headless=new flag for invisible background operations.
  • Session persistence across restarts, keeping the agent logged into platforms like GitHub, LinkedIn, or X.
  • Multi-tab management using targetId to pin the agent to specific browser windows.
  • Automated troubleshooting commands to kill stale processes and clear port conflicts for Openclaw Skills.
  • Direct protocol access which reduces latency compared to traditional extension-based relays.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*