leeguooooo
b6febbef39
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.
12 lines
524 B
Markdown
12 lines
524 B
Markdown
# Attribution
|
|
|
|
The chrome.debugger attach + CDP Target handling in `background.js` is adapted
|
|
from **openclaw-browser-relay** by chengyixu
|
|
(https://github.com/chengyixu/openclaw-browser-relay, MIT per its README).
|
|
|
|
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.agent_browser.connect`) — no port, no token,
|
|
Chrome authenticates the extension to the host by id. WebSocket/token/options
|
|
code removed.
|