stable-browser

What This Skill Does

The stable-browser skill replaces the fragile browser extension relay with a robust, direct connection to the Chrome DevTools Protocol (CDP). By bypassing the overhead of browser extensions and WebSocket-based relay services, this skill provides a stable, high-performance interface for all your automation needs. It runs a dedicated, headless-capable Chrome instance using a separate user profile, ensuring that your automation tasks are isolated from your main browsing activity. This architectural shift resolves common failure points such as WebSocket 403 errors, port conflicts, and random connection drops, making it the industry-standard choice for mission-critical tasks.

Installation

Installation is designed to be seamless. First, ensure you have the OpenClaw CLI configured, then run: clawhub install openclaw/skills/skills/jarvis563/stable-browser. Once installed, execute bash scripts/setup-cdp.sh. This script handles the heavy lifting: it creates a dedicated Chrome profile at ~/.chrome-debug-profile, sets up a persistent LaunchAgent on macOS for auto-starts, and updates your local configuration to point to the correct CDP endpoint. For manual configuration or custom ports, consult the references/manual-setup.md file within the skill repository.

Use Cases

This skill is perfect for complex automation workflows including persistent web scraping, automated social media posting, structured form filling, and high-frequency data extraction. Because it uses a dedicated profile, it is ideal for scenarios where you need to maintain login sessions for multiple services (e.g., GitHub, LinkedIn, or corporate dashboards) without interfering with your personal browsing. It is particularly effective for headless operations on servers where a GUI is unavailable.

Example Prompts

1. "Open the browser with profile=openclaw and navigate to https://github.com/issues, then take a full page snapshot."
2. "Using the stable-browser, fill out the application form at https://example.com/apply with the provided details and click the submit button."
3. "Start a headless session, login to my Twitter, and post the content generated in the previous step."

Tips & Limitations

To maximize reliability, always ensure you use profile="openclaw" in your browser commands. If you encounter a "Can't reach browser" error, verify that the remote debugging port is open using lsof -i :9222. For invisible background operations, you may modify the launch command to include --headless=new. Note that because this creates a separate profile, you must perform a one-time manual login for each site you plan to automate. If the browser becomes unresponsive due to a crash, use pkill -f 'remote-debugging-port=9222' to reset the connection instantly.