Stable OpenClaw browser automation using Chrome remote debugging and Playwright

✍️ OpenClawRadar📅 Published: February 26, 2026🔗 Source
Stable OpenClaw browser automation using Chrome remote debugging and Playwright
Ad

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=9222 pointed 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")
Ad

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

Ad

👀 See Also