browser-cash

What This Skill Does

The browser-cash skill empowers your OpenClaw agent with high-performance, unblocked browser sessions. By leveraging the Browser.cash infrastructure, this skill bypasses sophisticated anti-bot protections such as Cloudflare, DataDome, and perimeter firewalls. It provides a dedicated WebSocket CDP (Chrome DevTools Protocol) URL, allowing your agent to take control of a remote browser instance for tasks that require real-world interaction, rendering, and complex navigation.

Installation

To begin, ensure you have your API key from dash.browser.cash. Once obtained, register it with the system: clawdbot config set skills.entries.browser-cash.apiKey "your_key_here". Before your first execution, the skill requires Playwright and Puppeteer to communicate with the browser sessions. You can ensure the environment is ready by checking the directory ~/clawd/node_modules/playwright. If missing, the agent will prompt for installation or you can run cd ~/clawd && npm install playwright puppeteer-core to initialize the necessary dependencies.

Use Cases

This skill is perfect for scenarios where traditional HTTP requests fail. Use it for:

• Web Scraping: Extract data from protected e-commerce sites or social media platforms.
• Automated Testing: Verify UI functionality across different regions by setting session country codes.
• Form Automation: Bypass bot-detection when submitting forms or signing into applications.
• Screenshot/PDF Generation: Capture full-page renders of dynamic, JavaScript-heavy pages.

Example Prompts

1. "Open a session in Germany with a 1920x1080 resolution and navigate to example.com to scrape the main headlines."
2. "Use the 'my-session' profile to persist cookies, log into the dashboard, and extract the latest sales report table."
3. "Launch an unblocked browser session using a US proxy and take a high-resolution screenshot of the target URL."

Tips & Limitations

• Persistence: Always use the profile.name option if you need to keep cookies and session state across different automation runs.
• Resource Management: Browser sessions consume external resources; ensure you explicitly terminate sessions when your automation logic finishes to avoid unnecessary costs.
• Latency: CDP connections rely on stable network conditions. For best results, run your agent scripts in an environment with low latency to the servedBy node region.