Skip to content

Commit d3b29b9

Browse files
CodeGlimpseCodeGlimpse
committed
docs: 新增 OpenClaw 浏览器工具重构的中英文教程文档
新增两篇博客文章，分别以简体中文和英文撰写，详细介绍了 OpenClaw 2026.3.23.1 版本中浏览器自动化工具的重大重构。内容涵盖从旧版 Chrome 扩展中继模式迁移至新版基于 Chrome DevTools MCP 协议的原生连接方案，包括核心演进原因、新旧版本教程对比、关键技术点分析以及升级注意事项。
1 parent d1242e7 commit d3b29b9

2 files changed

Lines changed: 184 additions & 0 deletions

File tree

‎content/en/post/openclaw-chrome/index.md‎

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: "OpenClaw 2026.3.23.1 Browser Tool Overhaul: From Chrome Extension to Native DevTools MCP"
3+
description: "Based on official OpenClaw documentation and the latest from the Chrome team, this post details the major upgrade of the browser tool in version 2026.3.23.1, moving from extension-based relay to the native Chrome DevTools MCP protocol."
4+
slug: openclaw-chrome
5+
date: 2026-03-24 23:00:00+0800
6+
categories:
7+
- Tutorials
8+
tags:
9+
- OpenClaw
10+
---
11+
12+
In the latest **2026.3.23.1** release, OpenClaw has undergone a significant overhaul of its browser automation tools.
13+
14+
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.
15+
16+
---
17+
18+
## Core Evolution: Why No More Extensions?
19+
20+
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.
21+
22+
The new version introduces two core Profile modes:
23+
1. **`openclaw` Mode**: A fully isolated, managed browser that works out of the box with no configuration required (features an orange theme).
24+
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.
25+
26+
---
27+
28+
## Legacy Tutorial: Chrome Extension Relay
29+
30+
If you are still using an older version, the connection logic depends on a browser extension:
31+
32+
1. **Install Extension**: Go to `chrome://extensions/`, enable Developer Mode, and manually load the `openclaw-connector` folder.
33+
2. **ID Configuration**: Enter the unique ID generated by the extension into your `~/.openclaw/openclaw.json` (or the older YAML config).
34+
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.
35+
36+
---
37+
38+
## New Version Tutorial: DevTools MCP Remote Debugging (Recommended)
39+
40+
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+.
41+
42+
### Step 1: Enable Remote Debugging in Chrome
43+
No more complex command-line arguments. You can now enable this within Chrome's settings:
44+
1. Enter `chrome://inspect/#remote-debugging` in the Chrome address bar.
45+
2. Check **"Enable remote debugging"**.
46+
3. Follow the prompts to allow incoming debugging connections.
47+
48+
### Step 2: Configure OpenClaw to Use the `user` Profile
49+
OpenClaw configuration is now unified in `~/.openclaw/openclaw.json`. To enable native takeover, ensure your configuration looks like this:
50+
51+
```json
52+
{
53+
"browser": {
54+
"enabled": true,
55+
"defaultProfile": "user",
56+
"profiles": {
57+
"user": {
58+
"driver": "existing-session",
59+
"attachOnly": true,
60+
"color": "#00AA00"
61+
}
62+
}
63+
}
64+
}
65+
```
66+
67+
### Step 3: Authorize the Connection
68+
The first time you run `openclaw tool run browser`, a native authorization dialog will pop up at the top of Chrome.
69+
- Click **"Allow"**.
70+
- Chrome will then display a banner stating "Chrome is being controlled by automated test software," indicating the AI has successfully taken over.
71+
72+
---
73+
74+
## Key Technical Comparison
75+
76+
| Feature | Old (Extension) | New (DevTools MCP) |
77+
| :--- | :--- | :--- |
78+
| **Connection Protocol** | Extension API Forwarding | **Native CDP / MCP Protocol** |
79+
| **Authentication** | Extension ID Verification | **System-level Chrome Popup Authorization** |
80+
| **Session Sharing** | Requires extension intervention | **Native sharing of existing sessions** |
81+
| **Security** | Extension might have injection risks | **Based on Chrome's built-in security sandbox** |
82+
| **System Requirements** | Any Chrome version | **Chrome M144 or higher** |
83+
84+
---
85+
86+
## Upgrade Recommendations and Notes
87+
88+
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.
89+
2. **Config Path**: OpenClaw configuration has moved from `config.yaml` to the more standardized `~/.openclaw/openclaw.json`.
90+
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.
91+
92+
---

‎content/zh-cn/post/openclaw-chrome/index.md‎

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: "OpenClaw 2026.3.23.1 浏览器工具重构：从 Chrome 扩展转向原生 DevTools MCP"
3+
description: "参考 OpenClaw 官方文档与 Chrome 团队最新技术，详解 2026.3.23.1 版本 browser 工具的重大升级：弃用扩展中继，全面拥抱 Chrome DevTools MCP 协议。"
4+
slug: openclaw-chrome
5+
date: 2026-03-24 23:00:00+0800
6+
categories:
7+
- Tutorials
8+
tags:
9+
- OpenClaw
10+
---
11+
12+
在最新的 **2026.3.23.1** 版本中，OpenClaw 对浏览器自动化工具进行了重磅重构。
13+
14+
根据官方文档与 Chrome 团队的最新发布，OpenClaw 已正式从不稳定的“扩展插件中继（Extension Relay）”模式，转向了基于 **Chrome DevTools MCP (Model Context Protocol)** 的原生连接方案。这意味着 AI 现在能以更安全、更原生、更高效的方式接管你的浏览器。
15+
16+
---
17+
18+
## 核心演进：为什么不再需要插件？
19+
20+
在 2026.3.23.1 之前的版本中，OpenClaw 主要依靠一个手动安装的 Chrome 扩展来桥接。这种方式存在权限受限、登录态同步不稳定等问题。
21+
22+
新版本引入了两种核心 Profile（配置文件）模式：
23+
1. **`openclaw` 模式**：完全隔离的托管浏览器，无需任何配置，开箱即用（橙色主题）。
24+
2. **`user` 模式（原 `chrome` 模式升级）**：通过 **Chrome DevTools MCP** 直接附加到你当前正在使用的 Chrome 窗口，实现真正的“零插件”接管。
25+
26+
---
27+
28+
## 旧版本教程：Chrome 扩展中继 (Legacy)
29+
30+
如果你仍在使用旧版本，其连接逻辑依赖于扩展插件：
31+
32+
1. **安装扩展**：需进入 `chrome://extensions/` 开启开发者模式，手动加载 `openclaw-connector` 文件夹。
33+
2. **ID 配置**：在 `~/.openclaw/openclaw.json`（或旧版 YAML）中填入插件生成的唯一 ID。
34+
3. **手动点击**：每次任务开始前，用户必须在浏览器中点击插件图标，手动允许 AI 连接到当前标签页。
35+
36+
---
37+
38+
## 新版本教程：DevTools MCP 远程调试 (推荐)
39+
40+
在 **2026.3.23.1** 中，连接你的原生浏览器（Profile: `user`）不再需要插件，而是利用 Chrome 144+ 内置的远程调试能力。
41+
42+
### 第一步：在 Chrome 中开启远程调试
43+
不再需要繁琐的命令行参数，现在可以通过 Chrome 内部设置开启：
44+
1. 在 Chrome 地址栏输入 `chrome://inspect/#remote-debugging`。
45+
2. 勾选 **"Enable remote debugging"**。
46+
3. 按照提示允许传入的调试连接。
47+
48+
### 第二步：配置 OpenClaw 使用 `user` 配置文件
49+
OpenClaw 的配置现在统一在 `~/.openclaw/openclaw.json` 中。要启用原生接管，请确保配置如下：
50+
51+
```json
52+
{
53+
"browser": {
54+
"enabled": true,
55+
"defaultProfile": "user",
56+
"profiles": {
57+
"user": {
58+
"driver": "existing-session",
59+
"attachOnly": true,
60+
"color": "#00AA00"
61+
}
62+
}
63+
}
64+
}
65+
```
66+
67+
### 第三步：授权连接
68+
当你第一次运行 `openclaw tool run browser` 时，Chrome 顶部会弹出授权对话框。
69+
- 点击 **"Allow"**（允许）。
70+
- 此时 Chrome 会显示“Chrome 正受到自动测试软件的控制”横幅，表示 AI 已成功接管。
71+
72+
---
73+
74+
## 关键技术点对比
75+
76+
| 特性 | 旧版 (Extension) | 新版 (DevTools MCP) |
77+
| :--- | :--- | :--- |
78+
| **连接协议** | 扩展 API 转发 | **原生 CDP / MCP 协议** |
79+
| **认证方式** | 插件 ID 校验 | **Chrome 系统级弹窗授权** |
80+
| **登录态共享** | 需插件介入同步 | **原生共享现有 Session** |
81+
| **安全性** | 插件可能存在注入风险 | **基于 Chrome 内置安全沙箱** |
82+
| **系统要求** | 任意 Chrome 版本 | **Chrome M144 或更高版本** |
83+
84+
---
85+
86+
## 升级建议与注意事项
87+
88+
1. **版本要求**：原生 MCP 模式需要 **Chrome M144 (Beta/Canary)** 或更高版本。如果你使用的是稳定版 Chrome 且版本较低，建议继续使用 `openclaw` 托管模式。
89+
2. **配置文件路径**：OpenClaw 的配置已从 `config.yaml` 转向更加标准化的 `~/.openclaw/openclaw.json`。
90+
3. **隐私提示**：使用 `user` 模式时，AI 可以访问你已登录的所有页面（如 GitHub、Gmail）。在执行自动化任务时，请确保你信任该智能体。
91+
92+
---

0 commit comments

Comments
 (0)