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
Using Light-Context Cron Jobs for Daily OpenClaw Tips
A user shares their setup of a daily cron job that posts OpenClaw tips to a Nextcloud Talk channel, highlighting the --light-context flag to reduce bootstrap overhead for isolated tasks.
Agent-Ready Codebases: Negative Rules, Precise Names, Directory READMEs
A developer shares how CLAUDE.md rules, negative instructions, and precise naming cut token waste and prevented Claude Code from bloating classes like UserManager.
Building a Developer Portfolio with Claude Code: A Junior Dev's Workflow and Lessons Learned
A 21-year-old junior MERN stack dev shares how he built nidhil.live using Claude Code, emphasizing the importance of specific prompting and understanding generated code instead of blind copy-pasting.
Use CLAUDE.md to Persist Project Conventions Across Claude AI Sessions
Drop a CLAUDE.md file in your project root and Claude reads it at the start of every session, remembering your TypeScript rules, no default exports, testing conventions, and architecture context without re-explanation.