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
Routing cuts OpenClaw Max usage cost by 85%: $200/mo to $30/mo with API routing
A user tracked token usage and found only 15% of tasks need Opus. By routing routine work to Sonnet via API, monthly cost dropped from $200 to $30 with identical output quality.
Writing Effective SOUL.md Files for AI Coding Agents
A Reddit post from r/openclaw demonstrates the difference between vague and specific SOUL.md instructions, showing that specific prompts yield more useful AI agent behavior.
Claude's Research Output Varies by Language: Same Prompt, Different Sources
A Reddit test shows Claude returning different sources and developments across English, Chinese, Russian, Spanish, and Hindi prompts — same model, same structure, diverging results.
5 Patterns for Getting Better Results from Claude (Non-Technical Users)
Practical scaffolding, example-based prompting, negative instructions, persistent context, and source grounding — five patterns that consistently improve output quality from Claude, backed by six months of field experience.