Introduction

On March 13, 2026, OpenClaw released a game-changing feature update — Live Chrome Session Attach. This functionality leverages Chrome DevTools Protocol (CDP) and Model Context Protocol (MCP) to enable AI assistants to seamlessly take control of your actual Chrome browser session.

What is Live Chrome Session Attach?

In one sentence: “One-click takeover of your real Chrome browser session — preserving login states, no extension required.”

Traditional browser automation forces you to choose between:

  • Headless mode: Requires re-authentication on all sites, cannot use existing cookies
  • Extension mode: Requires installing Chrome extensions, manual per-tab attachment

Live Chrome Session Attach breaks through these limitations using the official Chrome DevTools MCP server.

Three Browser Control Modes Compared

ModeUse CaseLogin StateRequirementsTechnology
Built-in Chrome (default)Simple automation❌ Re-authentication neededBuilt-in, no installPlaywright
Extension Relay (legacy)Automation with login✅ PreservedChrome extension requiredCDP Relay
Live Session Attach ⭐(new)Real browser takeover✅ Full session preservedNo extensionChrome DevTools MCP

Chrome DevTools MCP Overview

Chrome DevTools MCP is Google’s official Model Context Protocol server that allows AI assistants to interact with Chrome browsers through a standardized MCP interface.

Key Features:

  • Based on Chrome DevTools Protocol (CDP)
  • Supports remote debugging of active browser sessions
  • Requires user to explicitly enable chrome://inspect/#remote-debugging
  • Fully preserves user login states and session cookies

Configuration Steps

Step 1: Enable Chrome Remote Debugging

Before using Live Session Attach, you must enable remote debugging in Chrome:

  1. Open Chrome Settings Page

    chrome://inspect/#remote-debugging

  2. Enable Remote Debugging

    • Find the “Remote Debugging” option
    • Toggle the switch to enable
    • Chrome will start a local debugging server (default port 9222)

  3. Verify Debugging Port

    # Visit in browser to see debuggable pages list
http://localhost:9222/json

Security Note: Remote Debugging listens on localhost (127.0.0.1) by default and won’t expose to external networks. OpenClaw communicates locally with this service.

Step 2: OpenClaw Configuration

Configure browser profiles in openclaw.json:

{
  "browser": {
    "profiles": {
      "user": {
        "type": "existing-session",
        "cdpUrl": "http://127.0.0.1:9222"
      },
      "openclaw": {
        "type": "managed"
      }
    },
    "defaultProfile": "user"
  }
}

Configuration Details:

  • "type": "existing-session" - Use existing Chrome session
  • "cdpUrl": "http://127.0.0.1:9222" - Chrome DevTools Protocol address
  • "defaultProfile": "user" - Default to user session mode

Step 3: Command Line Usage

# Check current browser connection status
openclaw browser status

# Connect to current Chrome session using user profile
openclaw browser snapshot --profile user

# Execute actions on specific tabs
openclaw browser click "Login Button" --profile user
openclaw browser type "input[name='search']" "OpenClaw" --profile user

Real-World Use Cases

Use Case 1: Automated Email Processing

# Prerequisite: You're logged into Gmail in Chrome
# Visit chrome://inspect/#remote-debugging to ensure it's enabled

openclaw browser snapshot --profile user  # View current page
# AI can see your Gmail interface and perform actions
"Mark all unread emails as read and archive them"

Use Case 2: Data Scraping (Login Required)

# Take over logged-in LinkedIn/Taobao/internal systems
openclaw browser --profile user

"Scrape my order list"
"Export my contacts"

Use Case 3: Cross-Platform Price Comparison

# Search across multiple platforms simultaneously
openclaw browser --profile user

"Search for iPhone 16 prices on Taobao, JD, and PDD"

Comparison with Legacy Methods

Legacy Method (Extension Relay)

Install extension → Click attach → Re-login → Start operation → Re-attach for new tabs

New Method (Live Session Attach via MCP)

# 1. Enable Chrome Remote Debugging (one-time setup)
chrome://inspect/#remote-debugging → Enable

# 2. Use directly
openclaw browser --profile user

Core Advantages:

  • ✅ Built on official Chrome DevTools MCP, more stable
  • ✅ Takes over your currently open Chrome window
  • ✅ Automatically preserves Gmail, GitHub, banking login states
  • ✅ No Chrome extension installation required
  • ✅ Automatic tab switching

Security

Security MeasureDescription
Local CommunicationChrome DevTools listens on 127.0.0.1 only, not exposed to network
User AuthorizationMust explicitly enable chrome://inspect/#remote-debugging
Token AuthenticationOpenClaw Gateway uses token authentication
Session IsolationWon’t affect other Chrome user profiles
Official ProtocolBased on Google’s official Chrome DevTools Protocol

Version Requirements

  • OpenClaw: 2026.3.13+
  • Chrome: Latest stable (DevTools MCP support)
  • Operating Systems: macOS / Linux / Windows

FAQ

Q: Why do I need to enable chrome://inspect/#remote-debugging?

A: This is Chrome’s official security design. Remote Debugging is disabled by default and must be explicitly enabled by the user to prevent unauthorized browser control by malicious software.

Q: Is my browser still secure after enabling Remote Debugging?

A: Yes. Remote Debugging listens on localhost (127.0.0.1) by default. External networks cannot connect directly. It’s safe as long as you don’t manually expose this port on public networks.

Q: Do I need to reconfigure after Chrome restarts?

A: Yes. Remote Debugging settings reset after Chrome restarts. You need to revisit chrome://inspect/#remote-debugging to re-enable.

Q: Can’t attach on macOS?

A: Known issue (GitHub Issue #46090). Ensure:

  1. Completely quit Chrome (Cmd+Q)
  2. Restart Chrome and enable Remote Debugging
  3. Restart OpenClaw Gateway

Written on March 15, 2026, based on OpenClaw 2026.3.13 and Chrome DevTools MCP official documentation