Files

T

leeguooooo 8a8106ad75 feat(connect): vendor MV3 connect extension (adapted from openclaw-browser-relay)

First step toward zero-confirmation direct connect to the user's real Chrome:
Chrome 136 killed --remote-debugging-port on the default profile, so the only
sanctioned way to drive the user's live logged-in window is an extension using
chrome.debugger (same approach as Codex/Claude, whose extensions are closed).

Vendors the MIT-licensed openclaw-browser-relay extension into
extensions/ab-connect/, rebranded to "agent-browser connect" (NOTICE.md keeps
attribution). It already handles the hard parts: chrome.debugger auto-attach all
tabs, new-tab auto-attach, MV3 service-worker keepalive (alarms) + reconnect,
sessionId↔tab mapping, token auth, and a CDP-over-WebSocket envelope
(connect handshake / forwardCDPCommand / forwardCDPEvent / ping-pong).

Inert for now — not wired. Next: an abs-daemon relay that speaks this envelope
and bridges it to the existing CdpClient (raw CDP), then a `connect` command.

2026-06-09 14:54:03 +09:00

419 B

Raw Blame History

Attribution

The ab-connect extension is adapted from openclaw-browser-relay by chengyixu — https://github.com/chengyixu/openclaw-browser-relay (MIT License, per its README).

Changes for agent-browser-stealth: rebranded; points at the agent-browser daemon's local relay endpoint instead of the OpenClaw gateway; protocol otherwise preserved (connect handshake, forwardCDPCommand/forwardCDPEvent, ping/pong).

419 B Raw Blame History

Attribution

419 B

Raw Blame History