Radar
← All projectsSunday, October 11, 2026
Chrome Relay
Your coding agent drives your real Chrome — signed in as you — in background tabs, with no remote-debug popup.
Why it matters
Chrome Relay is an open-source macOS stack that connects agent-browser CLIs to Google Chrome through a local relay and a small MV3 extension. Agents (Claude Code, Codex, Cursor, Paseo) open inactive tabs in a collapsed Agents group, run DevTools commands there, and never take window focus. Setup is opt-in per machine and per Chrome profile. A machine secret plus process checks keep random local tools and web pages from attaching.
Most agent browsers spin up a clean profile and die on SSO, 2FA, and the accounts you already use. Chrome Relay keeps the agent inside everyday Chrome so it can open the same dashboards, admin panels, and internal tools you already trust — without stealing focus or asking you to re-login every run.
How it works
Clone the repo, run bin/chrome-relay setup, then load the unpacked extension in each Chrome profile agents should use. Agents get a CDP URL from chrome-relay url and talk through agent-browser. Google account hops that are already signed in can auto-continue; password, passkey, or signed-out states stop and ask you. Every action lands in a daily JSONL audit under ~/.chrome-relay/audit. chrome-relay doctor and update cover health and upgrades.
Chrome DevTools MCP and headless agent browsers give a separate browser the agent owns. Chrome Relay is the opposite bet: keep your cookies, extensions, and logins, hide the agent in background tabs, skip the remote-debugging permission banner, and log what the agent did. Complementary to scrape/devtools stacks when the hard part is authenticated product UI, not raw HTML.
Similar tools