In the latest 2026.3.23.1 release, OpenClaw has undergone a significant overhaul of its browser automation tools.

According to official documentation and recent releases from the Chrome team, OpenClaw has officially transitioned from the unstable “Extension Relay” mode to a native connection scheme based on Chrome DevTools MCP (Model Context Protocol). This means AI can now take over your browser in a more secure, native, and efficient manner.

Core Evolution: Why No More Extensions?

Before version 2026.3.23.1, OpenClaw primarily relied on a manually installed Chrome extension to bridge the connection. This approach suffered from limited permissions and unstable session synchronization.

The new version introduces two core Profile modes:

1. openclaw Mode: A fully isolated, managed browser that works out of the box with no configuration required (features an orange theme).
2. user Mode (Upgraded from the old chrome mode): Directly attaches to your active Chrome window via Chrome DevTools MCP, achieving true “zero-extension” takeover.

Legacy Tutorial: Chrome Extension Relay

If you are still using an older version, the connection logic depends on a browser extension:

1. Install Extension: Go to chrome://extensions/, enable Developer Mode, and manually load the openclaw-connector folder.
2. ID Configuration: Enter the unique ID generated by the extension into your ~/.openclaw/openclaw.json (or the older YAML config).
3. Manual Authorization: Before each task, you must click the extension icon in the browser and manually allow OpenClaw to connect to the current tab.

New Version Tutorial: DevTools MCP Remote Debugging (Recommended)

In 2026.3.23.1, connecting to your native browser (Profile: user) no longer requires an extension. Instead, it utilizes the native remote debugging capabilities built into Chrome 144+.

Step 1: Enable Remote Debugging in Chrome

No more complex command-line arguments. You can now enable this within Chrome’s settings:

1. Enter chrome://inspect/#remote-debugging in the Chrome address bar.
2. Check “Enable remote debugging”.
3. Follow the prompts to allow incoming debugging connections.

Step 2: Configure OpenClaw to Use the user Profile

OpenClaw configuration is now unified in ~/.openclaw/openclaw.json. To enable native takeover, ensure your configuration looks like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

{
  "browser": {
    "enabled": true,
    "defaultProfile": "user",
    "profiles": {
      "user": {
        "driver": "existing-session",
        "attachOnly": true,
        "color": "#00AA00"
      }
    }
  }
}

Step 3: Authorize the Connection

The first time you run openclaw tool run browser, a native authorization dialog will pop up at the top of Chrome.

• Click “Allow”.
• Chrome will then display a banner stating “Chrome is being controlled by automated test software,” indicating the AI has successfully taken over.

Key Technical Comparison

Upgrade Recommendations and Notes

1. Version Requirements: Native MCP mode requires Chrome M144 (Beta/Canary) or higher. If you are using a stable version of Chrome with a lower version number, it is recommended to continue using the openclaw managed mode.
2. Config Path: OpenClaw configuration has moved from config.yaml to the more standardized ~/.openclaw/openclaw.json.
3. Privacy Reminder: When using user mode, the AI can access all pages where you are currently logged in (e.g., GitHub, Gmail). Ensure you trust the agent before performing automated tasks.