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.
This commit is contained in:
leeguooooo
2026-06-11 18:32:32 +09:00
parent 73cf32edc8
commit 3302762a32
+19 -4
View File
@@ -73,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