extensions/ab-connect.zip · id 锁定为 ciiljdlhdpfckdcfkphgmfalanpdejep为什么必须走商店:实测 Chrome 149 在非企业托管的 Mac 上,会把"非 Web Store"的 force-install 扩展直接标成 [BLOCKED]。商店扩展不受此限。这也是 codex / claude 扩展都发商店的原因。
debugger 权限,这是 Chrome Web Store 审核最严的权限之一。理由必须写清楚"只在用户本机、用户主动发指令时驱动用户自己的标签页,无远程服务器"。类似工具(如 claude-in-chrome)能过审,但可能被多问一轮、审核时间偏长(几天到一两周)。
https://chrome.google.com/webstore/devconsoleprivacy.html)extensions/ab-connect.zipciiljdlhdpfckdcfkphgmfalanpdejep(因为 manifest 里保留了 key,id 会被锁成这个,native messaging 的 allowed_origins 才对得上)。若 id 不是这个,告诉我,我重签。chrome-use
Let your own chrome-use CLI drive your logged-in Chrome — a local automation bridge. No remote server, no token.
chrome-use is the in-browser half of the open-source chrome-use CLI. It lets the command-line tool you installed on this same computer automate the Chrome you're already logged into — opening pages, clicking, filling forms, reading the DOM — driven entirely by you. How it works - The extension talks ONLY to the local chrome-use CLI over Chrome native messaging (a local inter-process channel — no network socket, no token, no remote server). - When you run an automation command, the extension relays Chrome DevTools Protocol operations to the tab you target, then returns the result to the CLI. Privacy - No analytics, no trackers, no data collection. - Nothing is sent to any remote server. The only message peer is the local CLI. - Source is open (Apache-2.0): https://github.com/leeguooooo/chrome-use You need the chrome-use CLI installed and paired (run: chrome-use extension install) for this extension to do anything.
Developer Tools
English
Bridge the user's locally-installed chrome-use CLI to their own logged-in Chrome so the CLI can automate pages the user is working with, entirely on the user's machine and at the user's command.
| 权限 | 理由（复制到对应输入框） |
|---|---|
| debugger | Attaches the Chrome DevTools Protocol to the user's own active tab so the paired local chrome-use CLI can automate it (navigate, click, read DOM) only while the user is running a command. Commands arrive solely from the local CLI via native messaging; there is no remote endpoint. |
| tabs | Enumerate and target the correct open tab to attach automation to. |
| tabGroups | Organizes the tabs the local chrome-use CLI drives into a labeled, colored Chrome tab group per automation session, so the user can see at a glance which tabs are under automation and they stay visually separated from the user's own tabs. |
| nativeMessaging | The sole communication channel: a local native-messaging connection to the chrome-use CLI installed on the same machine. No network is used. |
| storage | Persist small local pairing/configuration state for the extension. |
| alarms | Keep the MV3 service worker alive during longer automation sessions. |
| webNavigation | Detect page loads/navigations so automation can wait for the right moment before acting. |
| host permissions（若被问） | The extension declares none; tab access is mediated through the debugger attach the user initiates. |
privacy.html 的公开地址(见下)。商店要求一个公开可访问的隐私政策地址。GitHub Pages 已开启,直接填这个(渲染好看):
https://leeguooooo.github.io/chrome-use/extensions/store/privacy.html
(部署需 1–2 分钟生效。raw 备用直链:https://raw.githubusercontent.com/leeguooooo/chrome-use/main/extensions/store/privacy.html。)
可以截一张 CLI + Chrome 并排的演示图。需要的话我用 cua-driver 截一张合规尺寸的图给你。
extension install 的 force-install update_url 切到商店地址并发布新 fork;之后用户 extension install → 批准一次描述文件 → 静默装好(商店扩展不再 [BLOCKED]);或者用户在商店页一键 Add to Chrome。chrome://extensions → 打开开发者模式 → Load unpacked → 选 extensions/ab-connect,30 秒手动装一次,native messaging + extension connect 立即可用。等商店过审再切静默路径。