chore(release): 0.27.0-fork.35 — embed Store-install + feedback + stale-binary guidance in skill

Ships the post-fork.34 skill updates into the binary's embedded `skills get core`: - lead extension setup with the one-click Chrome Web Store install - nudge agents to file UX feedback at the GitHub issues page - when an agent hits the "Allow remote debugging?" dialog, self-check the version and upgrade a stale (<fork.30) build / remove a shadowing npm-pnpm copy Plus the README opening rewrite (hook-first vs Claude-in-Chrome / web-access / Playwright) and Chinese README — docs only, ride along.
docs(skill): guide agents to detect + upgrade a stale build on the consent dialog
2026-06-11 18:35:12 +09:00 · 2026-06-11 18:32:32 +09:00 · 2026-06-11 18:30:29 +09:00 · 2026-06-11 17:40:14 +09:00 · 2026-06-11 17:34:07 +09:00 · 2026-06-11 17:30:19 +09:00
6 changed files with 248 additions and 15 deletions
@@ -1,11 +1,42 @@
 # agent-browser-stealth

+**English** · [简体中文](README.zh.md)
+
 ![agent-browser-stealth](assets/hero.png)

 Stealth fork of [agent-browser](https://github.com/vercel-labs/agent-browser) — connects to your real Chrome, shares your login sessions, and is undetectable by anti-bot systems.

 For basic usage, commands, and API reference, see the [upstream documentation](https://github.com/vercel-labs/agent-browser).

+## Give your AI agent the browser you already live in
+
+**No fresh Chrome. No re-login. No "are you a robot?" walls.**
+
+agent-browser-stealth points **any** agent — Claude Code, Cursor, Codex, your own scripts — at the **Chrome you're already signed into everything on**. It clicks in *your* window, so you watch it work and grab the wheel the moment it hits a 2FA prompt or captcha. And because it's literally your real browser (over a one-click extension, native messaging — no debug port), sites read it as 100% human: **[CreepJS scores it 0% bot](#anti-detection).**
+
+**Why not just use…**
+
+- **Playwright / Puppeteer / browser-use?** They boot an *empty* browser — so you redo every login, fight every captcha, and still get flagged as automation. We use the session you already have.
+- **Claude's Chrome extension?** Great, but it only drives Claude. This drives *any* agent or CLI.
+- **A raw `--remote-debugging-port`** (web-access, etc.)? Chrome 136+ pops **"Allow remote debugging?"** on *every* connect. This never does — one-click Store extension, native messaging.
+
+<details>
+<summary><b>Full feature comparison</b> (the receipts)</summary>
+
+| | [Claude in Chrome](https://www.anthropic.com/claude/chrome) | web-access / raw CDP port | Playwright · Puppeteer · browser-use | **agent-browser-stealth** |
+|---|:---:|:---:|:---:|:---:|
+| Works with **any** agent / CLI (not one app) | ❌ Claude only | ✅ | ✅ | ✅ |
+| Drives your **real, logged-in** Chrome | ✅ | ✅ | ❌ fresh empty profile | ✅ |
+| **No "Allow remote debugging?" popup** | ✅ | ❌ every connect | — (own browser) | ✅ native messaging |
+| Real-browser fingerprint (CreepJS ~0%)¹ | ✅ | ✅ | ❌ automation markers / headless | ✅ **verified 0%** |
+| **No `Runtime.enable` CDP leak** (rebrowser)² | — | ❌ leaks | ❌ leaks | ✅ **off by default** |
+| Many agents on **one** real Chrome, isolated tab groups³ | ❌ single app | ⚠️ shared tabs, no isolation | ❌ separate browsers | ✅ |
+| Permissions footprint | 16 incl. `<all_urls>` | full CDP | full control | **7, no `<all_urls>`** |
+
+<sub>¹ All three real-Chrome tools score ~0% on CreepJS (it's a real browser); we've measured ours. ² rebrowser's `runtimeEnableLeak` — verified clean on our relay path; Claude in Chrome not independently tested (—). ³ web-access can run parallel sub-agents on one browser, but without per-session isolation; each `--session` here gets its own colored, command-isolated tab group. See [Anti-detection](#anti-detection) for the measured numbers.</sub>
+
+</details>
+
 ## Why this fork?

 <img src="assets/fingerprint.png" alt="real but undetectable fingerprint" width="300" align="right" />
@@ -100,12 +131,26 @@ fresh one.

 ## Setup: connect to your Chrome

-Attaching uses the Chrome DevTools Protocol, which Chrome only exposes when it is
-**launched with a remote-debugging port**. This is a startup flag, not a setting
-— the `chrome://inspect` toggle alone is **not** enough (it only enables target
-discovery, not the CDP attach).
+**Recommended — the browser extension (one click, no popups).** Install the
+[**agent-browser-stealth** extension from the Chrome Web Store](https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk),
+then register the local bridge once:

-**Recommended — fully quit Chrome, then relaunch with the port:**
+```bash
+agent-browser extension install      # register the native-messaging host (one-time)
+agent-browser open https://x.com/home
+```
+
+`agent-browser open` then drives your real, logged-in Chrome over **native
+messaging** — no debug port, no token, and **no "Allow remote debugging?" dialog,
+ever**. The extension auto-updates and survives Chrome restarts, so it stays
+connected with zero per-use confirmation (ideal for unattended/agent use).
+
+<details>
+<summary>Alternative — raw remote-debugging port (pops a consent dialog)</summary>
+
+Without the extension, agent-browser attaches over the Chrome DevTools Protocol,
+which Chrome only exposes when **launched with a remote-debugging port** (a
+startup flag — the `chrome://inspect` toggle alone is not enough):

 ```bash
 # macOS
@@ -115,9 +160,10 @@ google-chrome --remote-debugging-port=9222
 # Windows: add --remote-debugging-port=9222 to your Chrome shortcut's target
 ```

-Then run `agent-browser open <url>` — it auto-discovers the port and attaches.
-On first attach, **Chrome 136+ shows an "Allow remote debugging?" dialog — click
-Allow once** (it persists for that Chrome session).
+Then `agent-browser open <url>` auto-discovers the port. On first attach,
+**Chrome 136+ shows an "Allow remote debugging?" dialog** — click Allow once (it
+persists for that Chrome session). The extension above avoids this entirely.
+</details>

 **No setup / don't want to touch your real Chrome?** Use
 `agent-browser --launch open <url>` to spawn a fresh isolated stealth browser
@@ -0,0 +1,165 @@
+# agent-browser-stealth
+
+[English](README.md) · **简体中文**
+
+![agent-browser-stealth](assets/hero.png)
+
+[agent-browser](https://github.com/vercel-labs/agent-browser) 的隐身分支 —— 直接连接**你自己**正在用的、已登录的 Chrome，复用你的登录态，对反爬/反自动化系统**完全不可检测**。
+
+基础用法、命令与 API 参考见[上游文档](https://github.com/vercel-labs/agent-browser)。
+
+## 把你**已经登录好**的浏览器，交给你的 AI agent
+
+**不用开新 Chrome。不用重新登录。不用跟"你是不是机器人"较劲。**
+
+agent-browser-stealth 让**任意** agent（Claude Code、Cursor、Codex、你自己的脚本）直接操作你**已经登录了所有网站**的那个 Chrome。它在**你的窗口里**点击，你看着它干活，撞到 2FA / 验证码的瞬间你接管一下，它接着跑。因为它**就是你的真实浏览器**（一键装的扩展、原生消息、无调试端口），网站眼里它 100% 是人：**[CreepJS 实测 0% 机器人](#反检测)。**
+
+**为什么不用……**
+
+- **Playwright / Puppeteer / browser-use？** 它们开的是**空**浏览器 —— 每个登录你重做、每个验证码你硬扛、最后还被标成自动化。我们直接用你**现成的**会话。
+- **Claude 的 Chrome 插件？** 很好，但**只能给 Claude 用**。我们给**任意** agent / CLI 用。
+- **裸 `--remote-debugging-port`**（web-access 等）？ Chrome 136+ **每次连都弹** "Allow remote debugging?"。我们**永不弹** —— 商店一键装，原生消息。
+
+<details>
+<summary><b>完整对比矩阵</b>（要细节的看这里）</summary>
+
+| | [Claude in Chrome](https://www.anthropic.com/claude/chrome) | web-access / 裸 CDP 端口 | Playwright · Puppeteer · browser-use | **agent-browser-stealth** |
+|---|:---:|:---:|:---:|:---:|
+| **任意** agent / CLI 都能用（不绑单一 app） | ❌ 仅 Claude | ✅ | ✅ | ✅ |
+| 驱动你**真实、已登录**的 Chrome | ✅ | ✅ | ❌ 全新空 profile | ✅ |
+| **不弹 "Allow remote debugging?"** | ✅ | ❌ 每次连都弹 | —（自带浏览器） | ✅ 原生消息 |
+| 真实浏览器指纹（CreepJS ~0%）¹ | ✅ | ✅ | ❌ 自动化特征 / headless | ✅ **已实测 0%** |
+| **无 `Runtime.enable` CDP 泄漏**（rebrowser）² | — | ❌ 泄漏 | ❌ 泄漏 | ✅ **默认关闭** |
+| 多 agent 共用**同一个**真实 Chrome、标签组隔离³ | ❌ 单 app | ⚠️ 共享 tab、无隔离 | ❌ 各开各的浏览器 | ✅ |
+| 权限面 | 16 个，含 `<all_urls>` | 完整 CDP | 完全控制 | **7 个，无 `<all_urls>`** |
+
+<sub>¹ 三家"真实 Chrome"工具在 CreepJS 上都 ~0%（毕竟是真浏览器），我们的是实测过的。² rebrowser `runtimeEnableLeak` —— 我们的中继路径实测无泄漏；Claude in Chrome 未独立测试（—）。³ web-access 也能跑并行子 agent，但无每会话隔离；本工具每个 `--session` 拿到自己彩色、命令隔离的标签组。实测数字见 [反检测](#反检测)。</sub>
+
+</details>
+
+## 为什么要 fork
+
+<img src="assets/fingerprint.png" alt="真实但不可检测的指纹" width="300" align="right" />
+
+**agent-browser**（上游）启动的是空 profile 的全新浏览器：你得重新登录，网站也能看出是自动化。
+
+**agent-browser-stealth** 连接你**现有**的 Chrome —— cookies、会话、浏览器指纹全是真的，因为它**就是**你的真实浏览器。
+
+| | agent-browser | agent-browser-stealth |
+|---|---|---|
+| 浏览器 | 启动新 Chrome | 连接你的 Chrome |
+| 登录态 | 空，要重新登 | 你现有的会话 |
+| 指纹 | 带自动化标记 | 你的真实指纹 |
+| 协作 | 独立窗口 | 同一窗口，随时接管 |
+| 验证码 | Agent 卡住 | 你点一下，Agent 继续 |
+
+## 工作原理
+
+![工作原理](assets/how-it-works.png)
+
+你的 **agent-browser CLI** 通过 Chrome **原生消息（native messaging）** 和一个小**浏览器扩展**通信 —— 这是本机进程间通道，**无网络端口、无 token、无远程服务器**。扩展用 `chrome.debugger` 驱动你指定的标签页（在你**已登录**的 Chrome 里），再把结果交还给 CLI。全程都在你本机。
+
+![架构](assets/architecture.png)
+
+每个 `--session` 拿到**自己的彩色标签组**，多个 agent 共用同一个真实浏览器、互不干扰，也不动你自己的标签页。
+
+## 安装
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/leeguooooo/agent-browser-stealth/main/install.sh | sh
+```
+
+从最新的 [GitHub Release](https://github.com/leeguooooo/agent-browser-stealth/releases) 下载对应平台的预编译二进制，安装 `agent-browser`（以及 `abs` 别名）。无需 npm，无需 token。
+
+### 安装 AI agent skills
+
+```bash
+npx skills add leeguooooo/agent-browser-stealth
+```
+
+把 `skills/agent-browser` 拉进当前项目，让你的 AI agent 拿到正确的用法和预授权的 bash 权限。
+
+## 连接你的 Chrome
+
+**推荐 —— 浏览器扩展（一键，无弹窗）。** 从 Chrome 应用商店安装 [**agent-browser-stealth** 扩展](https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk)，再注册一次本地桥：
+
+```bash
+agent-browser extension install      # 注册原生消息 host（一次性）
+agent-browser open https://x.com/home
+```
+
+之后 `agent-browser open` 就通过**原生消息**驱动你真实、已登录的 Chrome —— 无调试端口、无 token、**永远不弹 "Allow remote debugging?"**。扩展自动更新、重启不掉，零确认（适合无人值守 / agent 场景）。
+
+<details>
+<summary>备选 —— 裸 remote-debugging 端口（会弹同意框）</summary>
+
+不装扩展时，agent-browser 退回用 CDP 连接，而 Chrome 只在带 remote-debugging 端口启动时才暴露它：
+
+```bash
+# macOS
+open -a "Google Chrome" --args --remote-debugging-port=9222
+# Linux
+google-chrome --remote-debugging-port=9222
+# Windows: 给 Chrome 快捷方式 target 加 --remote-debugging-port=9222
+```
+
+然后 `agent-browser open <url>` 自动发现端口。首次连接 **Chrome 136+ 会弹 "Allow remote debugging?"** —— 点一次 Allow（该 Chrome 会话内持续有效）。上面的扩展则完全避开这个框。
+</details>
+
+## 用法
+
+```bash
+# 连接你的 Chrome 并导航
+agent-browser open https://example.com
+
+# 一切都在你已登录的浏览器里进行
+agent-browser click "Post"
+agent-browser fill "Title" "Hello World"
+agent-browser screenshot ./page.png
+```
+
+Agent 在你的 Chrome 里操作 —— 你能实时看到开标签、加载、点击。任意时刻都能接管（比如手动过验证码），然后让 agent 继续。
+
+### 独立模式（`--launch`）
+
+```bash
+# 临时：全新空 profile —— 无 cookie 无登录（适合 CI / 测试）
+agent-browser --launch open https://example.com
+
+# 保留登录：用你真实的 Chrome profile 启动
+agent-browser --launch --profile auto open https://x.com/home
+```
+
+## 反检测
+
+连接你真实 Chrome 时，我们**零** JS 注入 —— 浏览器指纹完全是真的。指导原则是 **native CDP/Chrome 覆盖优先于 JS 谎言**：被重定义的 getter 本身可被检测，原生覆盖则不会。
+
+- `navigator.webdriver = false` 走 `Emulation.setAutomationOverride`（原生，CreepJS 类说谎检测查不出）。
+- **`Runtime.enable` 默认关闭** —— 活着的 `Runtime` 域是可被检测的 CDP 信号（patchright/rebrowser 的 "runtime leak"），即便连的是你真实 Chrome。只在你主动开启 console/错误捕获时才启用。
+
+**实测结果（连接真实 Chrome，中继路径）：**
+
+| 检测站 | 结果 |
+|---|---|
+| [CreepJS](https://abrahamjuliot.github.io/creepjs/) | **0% stealth · 0% headless**（零 override 痕迹） |
+| [bot.incolumitas.com](https://bot.incolumitas.com/) | 全部 OK（overflowTest / overrideTest / puppeteerExtraStealth / worker 一致性） |
+| [rebrowser-bot-detector](https://bot-detector.rebrowser.net/) | `runtimeEnableLeak` 🟢 · `pwInitScripts` 🟢 |
+| [bot.sannysoft.com](https://bot.sannysoft.com) | 全绿 |
+
+`--launch` 独立模式下会改用一整套隐身补丁，同样过上述检测。
+
+## 与上游的差异
+
+基于 [agent-browser v0.27.0](https://github.com/vercel-labs/agent-browser)：
+
+- **默认 auto-connect** —— `agent-browser open` 连你的 Chrome 而非启新的
+- **CDP 原生隐身** —— `Emulation.setAutomationOverride` 而非 JS 补丁
+- **双隐身模式** —— 真实 Chrome 零补丁，`--launch` 全补丁
+- **`--launch` / `--new`** —— 显式启动独立浏览器
+- **CI 自动检测** —— 设了 `CI` 环境变量时走独立模式
+
+所有上游功能（命令、快照、截图、录制、标签、会话等）保持一致。
+
+## License
+
+Apache-2.0（与上游一致）
@@ -45,7 +45,7 @@ dependencies = [

 [[package]]
 name = "agent-browser-stealth"
-version = "0.27.0-fork.34"
+version = "0.27.0-fork.35"
 dependencies = [
 "aes-gcm",
 "async-trait",
@@ -1,6 +1,6 @@
 [package]
 name = "agent-browser-stealth"
-version = "0.27.0-fork.34"
+version = "0.27.0-fork.35"
 edition = "2021"
 description = "Fast browser automation CLI for AI agents"
 license = "Apache-2.0"
@@ -1,6 +1,6 @@
 {
  "name": "agent-browser-stealth",
-  "version": "0.27.0-fork.34",
+  "version": "0.27.0-fork.35",
  "description": "Browser automation CLI for AI agents — stealth fork with anti-detection",
  "type": "module",
  "packageManager": "pnpm@11.1.3",
@@ -15,6 +15,13 @@ Most normal web tasks (navigate, read, click, fill, extract, screenshot) are
 covered here. Load a specialized skill when the task falls outside browser
 web pages — see [When to load another skill](#when-to-load-another-skill).

+> **Hit a rough edge? Please report it.** If a command surprised you — a
+> confusing error, a stale `@ref`, an occluded click, a flaky wait, a missing
+> feature, or anything that cost you extra turns — open a quick issue at
+> **<https://github.com/leeguooooo/agent-browser-stealth/issues>** with the exact
+> command and what happened vs. what you expected. Agent-filed friction reports
+> are how this tool gets sharper; a 30-second issue is genuinely valuable.
+
 ## The core loop

 ```bash
@@ -66,10 +73,25 @@ popup never fires. `agent-browser extension connect` is the explicit form of the
 same path. Zero-confirmation, zero-token. Use `--launch` instead when a fresh,
 isolated browser is fine.

-**If you DO hit the "Allow remote debugging?" dialog**, the relay wasn't live, so
-`open` fell back to the raw debug port. Don't keep retrying — tell the user to
-install the Store extension above (one click); after that the relay stays up and
-the dialog never returns.
+**If you DO hit the "Allow remote debugging?" dialog**, don't keep retrying (every
+attempt re-pops it). One of two things is true:
+
+1. **You're on a stale build.** The relay-preference that avoids this dialog
+   landed in **fork.30**. Run `agent-browser --version`: if it's below
+   `0.27.0-fork.30`, upgrade and retry:
+   ```bash
+   curl -fsSL https://raw.githubusercontent.com/leeguooooo/agent-browser-stealth/main/install.sh | sh
+   ```
+   If `which -a agent-browser` shows more than one install, an old **npm/pnpm**
+   copy (the npm registry lags behind — Releases are the source of truth) may be
+   shadowing the upgraded one; remove the stale copy
+   (`npm rm -g agent-browser-stealth` / `pnpm rm -g agent-browser-stealth`) so the
+   `install.sh` build wins. A tool that bundles its *own* pinned copy
+   (e.g. `node .../agent-browser-stealth@0.24.x/.../agent-browser`) needs that
+   copy upgraded too.
+2. **The extension/relay isn't live.** Tell the user to install the Store
+   extension (one click, above); after that the relay stays up and the dialog
+   never returns.

 Each `--session` that connects gets its **own colored Chrome tab group** (named
 after the session) and drives only its own tabs — multiple agents share the one
Author	SHA1	Message	Date
leeguooooo	9ac8bae981	chore(release): 0.27.0-fork.35 — embed Store-install + feedback + stale-binary guidance in skill Release binaries / Build macOS ARM64 (push) Has been cancelled Release binaries / Build macOS x64 (push) Has been cancelled Release binaries / Build Linux ARM64 (push) Has been cancelled Release binaries / Build Linux musl ARM64 (push) Has been cancelled Release binaries / Build Linux musl x64 (push) Has been cancelled Release binaries / Build Linux x64 (push) Has been cancelled Release binaries / Build Windows x64 (push) Has been cancelled Release binaries / Attach binaries to GitHub Release (push) Has been cancelled Ships the post-fork.34 skill updates into the binary's embedded `skills get core`: - lead extension setup with the one-click Chrome Web Store install - nudge agents to file UX feedback at the GitHub issues page - when an agent hits the "Allow remote debugging?" dialog, self-check the version and upgrade a stale (<fork.30) build / remove a shadowing npm-pnpm copy Plus the README opening rewrite (hook-first vs Claude-in-Chrome / web-access / Playwright) and Chinese README — docs only, ride along.	2026-06-11 18:35:12 +09:00
leeguooooo	3302762a32	docs(skill): guide agents to detect + upgrade a stale build on the consent dialog Other users will hit the same "古董二进制" problem — an agent-browser-stealth predating the relay-preference (fork.30) ignores the extension relay and pops Chrome 136+'s "Allow remote debugging?" dialog. So when an agent hits that dialog, the skill now says to: 1. check `agent-browser --version`; if < 0.27.0-fork.30, upgrade via install.sh (the npm registry lags — Releases are source of truth), and remove any stale npm/pnpm copy that shadows it (a tool bundling its own pinned copy needs that upgraded too); 2. otherwise install the Store extension. Stops the "keep retrying the raw port" loop.	2026-06-11 18:32:32 +09:00
leeguooooo	73cf32edc8	docs(skill): encourage agents to file UX feedback to GitHub issues Add a prominent callout near the top of the core skill asking agents that hit a rough edge (confusing error, stale @ref, occluded click, flaky wait, missing feature) to open a quick issue at https://github.com/leeguooooo/agent-browser-stealth/issues with the command and expected-vs-actual. Agent-filed friction is the cheapest, highest-signal way to sharpen the tool (the Hermes dogfood runs already proved this).	2026-06-11 18:30:29 +09:00
leeguooooo	85fd019f62	docs: lead with the hook, not a feature matrix The comparison read like a checklist (Runtime.enable leak, permissions footprint — proof, not pitch). Reframe the opening around the visceral wins: - headline: "Give your AI agent the browser you already live in" - pain→relief lead: no fresh Chrome, no re-login, no captcha walls; you watch it work and take the wheel on 2FA; undetectable because it IS your browser (0% bot) - three plain "why not just use X?" lines (Playwright/browser-use, Claude in Chrome, raw debug port) instead of a wall of checkmarks - the honest feature matrix moves into a collapsible "Full feature comparison". Mirrored in README.zh.md.	2026-06-11 17:40:14 +09:00
leeguooooo	9b4d924e48	docs: make the comparison table honest (CreepJS, Runtime.enable, multi-agent) Reader fact-checked the table — three rows overclaimed: - CreepJS: all real-Chrome tools (Claude in Chrome, web-access, us) score ~0%; it is NOT a win vs them. Reframe as "real-browser fingerprint" (✅ for all three, ❌ for Playwright/Puppeteer); note ours is the measured one. - Runtime.enable leak: mark Claude in Chrome "—" (not independently tested) rather than ✅; web-access/Playwright leak, ours is off by default (rebrowser-verified). - Multi-agent: web-access CAN run parallel sub-agents (shared browser), so not ❌. The real differentiator is per-session ISOLATED, command-scoped tab groups. Added footnotes spelling out the caveats. Same fixes in README.zh.md.	2026-06-11 17:34:07 +09:00
leeguooooo	9ad011d93c	docs: add "why not X" comparison up top + Chinese README - README opens with a head-to-head vs Claude in Chrome / web-access (raw CDP) / Playwright·Puppeteer·browser-use: the only tool that drives your own logged-in Chrome, from any agent, with no consent popup, undetectably (CreepJS 0%), and multi-agent — addresses the recurring "why not just use <alternative>" question. - add README.zh.md (简体中文) with a language switcher in both files.	2026-06-11 17:30:19 +09:00
leeguooooo	ebd220274b	docs(README): lead "connect to your Chrome" with the Chrome Web Store extension The extension is live on the Web Store, so make the one-click, no-popup extension path the recommended setup (native messaging — no debug port, no token, no "Allow remote debugging?" dialog, restart-stable). Demote the raw --remote-debugging-port method to a collapsed "Alternative" that notes it pops the consent dialog.	2026-06-11 17:24:49 +09:00