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 Code Works Better as Code Reviewer Than Generator
A developer shares that Claude Code produces more grounded output when used to review existing code rather than generate from scratch. Key practices include starting sessions with current implementations, maintaining project context files, and restarting sessions when responses degrade.
Code Patterns Beat AI Guidelines: Porting a Firefox Extension to Chrome
A developer failed twice to port a Firefox extension to Chrome using AI prompts, then succeeded by extracting browser-agnostic core logic with a BrowserShell interface, reducing Chrome-specific code to 5 meaningful lines.
Skippy's Private LLM: How I Solved OpenClaw's Ollama Sub-Agent Timeout by Calling Ollama Directly
An OC COO's AI assistant bypasses OpenClaw's broken sub-agent system by calling a second Ollama instance directly via curl. No gateway, no event loop blocking.
Fix Ollama Cloud Model maxTokens: Cap is 16K, Not Config Value
Ollama cloud caps output at 16,384 tokens regardless of maxTokens config. Set to 14,000 to avoid EOF errors. Restructure long outputs or route to direct provider.