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
OpenClaw Drift Fix: Four Operator Skills to Harden Agent Workflows
A developer shares four operator skills — Outcome Guard, Direction Clarifier, Routing Enforcer, Completion Verifier — to stop agents from drifting and calling tasks done prematurely.
Claude Agent Sends Memes via Discord Using Tenor GIFs — Full Protocol
A Claude code agent setup adds context‑aware emoji reactions, one‑sentence status messages, and validated Tenor GIF URLs to every Discord transport message, with explicit web search and fetch steps to avoid dead links.
Reddit user shares prompt structure to reduce Claude Code output drift in complex tasks
A Reddit user found that using a structured prompt layout for longer Claude Code tasks helps prevent output drift. The approach involves defining specific elements like task scope, required files, success criteria, and avoidance parameters before execution.
Field Report: Qwen 3.6 27B on an M2 MacBook Pro (32GB) – Painfully Slow but Smart Output
Running Qwen 3.6 27B IQ4_XS on an M2 MacBook Pro with 32GB RAM yields 7.9 t/s initially, degrading to 3.1 t/s at 52k context. Code quality impresses, but memory bandwidth is the bottleneck.