Stable OpenClaw browser automation using Chrome remote debugging and Playwright
A developer on r/openclaw shared a practical workaround for persistent browser automation sessions with OpenClaw, addressing reliability issues with the built-in browser and Chrome extension relay.
The Problem
According to the source, OpenClaw's built-in browser is unreliable. The Chrome extension relay detaches after a use or two, requiring manual reconnection via the toolbar icon each time. This makes it unusable when away from the desk or on mobile. The developer tried different Chrome profiles, restarting the gateway multiple times, and adjusting configuration without success.
The Solution
The working method involves:
- Launching Chrome with the command-line flag:
--remote-debugging-port=9222pointed at its own user data folder - Logging into services (Amazon, Gmail, X, etc.) so cookies persist
- Connecting Playwright using:
chromium.connect_over_cdp("http://localhost:9222")
Results
After two hours of testing, the developer reported zero restarts and zero manual reconnects. The setup successfully handled searching Amazon, adding items to cart, generating images with Grok and Gemini, and running web searches without disconnections. The developer described this as "a completely different experience" compared to the extension-based approach.
📖 Read the full source: r/openclaw
👀 See Also
CLAUDE.md Entries That Disable Opus 4.7’s Human-Pacing Behavior
Three CLAUDE.md directives that suppress Claude 4.7 Opus's break suggestions, time overestimates, and phase-splitting during long coding sessions.
Walking and Dictating with Claude Code: A Practical Setup
A developer shares their setup: walking 2-3 hours daily while dictating prompts to Claude Code via OpenAI Whisper, using a remote control or cowork chats.
Claude's Data Sources: When to Request Web Searches for Current Information
Claude sometimes relies on internal training data instead of performing web searches, which may provide outdated information. Users can request web searches specifically to get more current results.
Fixing AI Agent Dumbness: A Shared Context Tree per Repo
The reason AI employees feel dumb isn't the model—it's lack of shared context. One developer's fix: a context tree repo with hierarchical markdown nodes, auto-maintained by the agent.