docs(skill): lead extension setup with the published Chrome Web Store build

The extension is now live on the Web Store
(knfcmbamhjmaonkfnjhldjedeobeafmk). Update the skill so agents:
- install from the Store (one-click, restart-stable, auto-updating) as the
  primary path, with Load-unpacked demoted to a dev fallback (it can be disabled
  on Chrome restart, silently dropping the relay).
- when they DO hit the "Allow remote debugging?" dialog (relay not live → raw-port
  fallback), stop retrying and tell the user to install the Store extension once,
  rather than repeatedly popping the consent dialog.
This commit is contained in:
leeguooooo
2026-06-11 17:10:52 +09:00
parent 5d202c06a6
commit bc9622994e
2 changed files with 30 additions and 19 deletions
+9 -8
View File
@@ -331,15 +331,16 @@ One-time setup:
agent-browser extension install # writes the native-messaging host manifest
```
The native-messaging host accepts **both** extension origins, so the extension
can be installed either way:
The native-messaging host accepts **both** extension origins, so either install
works — but prefer the Store build:
1. **Load unpacked (works today)** — load `<repo>/extensions/ab-connect` from
source; its pinned `key` gives the stable id `ciiljdlhd…`.
2. **Chrome Web Store (once published)** — one-click *Add to Chrome*; the store
strips the `key` and assigns its own id (`knfcmbamhjmaonkfnjhldjedeobeafmk`),
which `connect.rs` also allow-lists. (Submitted for review; until it's live,
use Load unpacked.)
1. **Chrome Web Store (recommended)** — one-click *Add to Chrome*:
<https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk>
Restart-stable and auto-updating (store id `knfcmbamhjmaonkfnjhldjedeobeafmk`).
2. **Load unpacked (dev)** — load `<repo>/extensions/ab-connect` from source;
its pinned `key` gives the stable id `ciiljdlhd…`. NOTE: Load-unpacked
extensions can be disabled/dropped on Chrome restart (Developer-mode handling),
which silently drops the relay — so for unattended setups use the Store build.
For Load unpacked — a GUI step (Chrome's `chrome://extensions` is privileged; the
CLI can't load an unpacked extension):