OpenClaw Adds Chrome DevTools MCP: Debug Live Browser Sessions from Your AI Agent

OpenClaw 2026.3.13-beta.1 shipped with a quietly powerful feature: official Chrome DevTools MCP attach mode. Your AI agent can now debug live Chrome sessions alongside you.

Goal

Configure OpenClaw to attach to your existing Chrome browser session using the Chrome DevTools Protocol for debugging and automation.

Prerequisites

OpenClaw 2026.3.13+
Google Chrome or Chromium
Chrome started with remote debugging flag

Steps

1. Enable Chrome remote debugging

Start Chrome with the debugging port:

# macOS
open -a "Google Chrome" --args --remote-debugging-port=9222

# Linux
google-chrome --remote-debugging-port=9222

# Windows
chrome.exe --remote-debugging-port=9222

Or visit chrome://inspect/#remote-debugging to enable.

2. Configure OpenClaw for user profile

Use the new profile="user" option to target your logged-in browser:

# Browser action with user profile
browser_action(
    action="open",
    url="https://example.com",
    profile="user"
)

3. Use Chrome Relay for extension-based control

For the Chrome extension relay flow, use profile="chrome-relay":

browser_action(
    action="act",
    selector="button#submit",
    profile="chrome-relay"
)

Verify

# Test DevTools connectivity
chrome_devtools_http://localhost:9222/json/version

# Should return Chrome version info and available pages