oimwiodev/chrome-use
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(connect): keep native-messaging host as com.agent_browser.connect (no relay break)

Browse Source 
Reverting the host-name rename from the chrome-use rebrand. The host name is
invisible internal plumbing (lives only in NativeMessagingHosts/*.json and the
extension), so renaming it to com.leeguoo.chrome_use bought nothing user-facing
but broke the relay for every existing user: the new chrome-use binary couldn't
find a matching host/extension, silently fell back to raw --remote-debugging-port,
and re-popped the 'Allow remote debugging?' consent dialog.

Keeping com.agent_browser.connect means the renamed chrome-use binary keeps
working with the already-installed host json and the live ab-connect 0.4.2
extension — zero relay break, no dialog, and the store republish becomes an
OPTIONAL cosmetic display-name update (manifest bumped 0.5.0 → 0.4.3, name stays
chrome-use). Only the binary/command name changed for users.
This commit is contained in:
leeguooooo
2026-06-12 14:07:10 +09:00
parent 5addb94dc4
commit b6febbef39
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
extensions/ab-connect/NOTICE.md
+1 -1
View File
@@ -6,6 +6,6 @@ from **openclaw-browser-relay** by chengyixu
Changes for chrome-use: rebranded to "chrome-use connect"; the
transport is rewritten from a localhost WebSocket + shared token to Chrome
**native messaging** (host `com.leeguoo.chrome_use`) — no port, no token,
**native messaging** (host `com.agent_browser.connect`) — no port, no token,
Chrome authenticates the extension to the host by id. WebSocket/token/options
code removed.