agent-chrome-relay
Let your AI agents use your Chrome, signed in as you, in background tabs. By Alexey Indeev · blog: read.aindeev.com · X: @AlexeyIndeev
- agent-browser
- ai-agents
- browser-automation
- cdp
- chrome-extension
- claude
- claude-code
- codex
- cursor
- macos
- paseo
- Stars
- 251
- Forks
- 3
- + today
- +3
- Created
- 1d
Ranking data as of October 11, 2026 (UTC).
Star History
Today, hour by hour
Overview
Let your AI agents use your Chrome, signed in as you, in background tabs. By Alexey Indeev · blog: read.aindeev.com · X: @AlexeyIndeev It ranks #109 on GitTiger, gaining +3 stars on October 11, 2026 (UTC).
The project is written in Go and has 3 forks. It was created 1d ago.
What it is
The description says it "lets your AI agents use your Chrome, signed in as you, in background tabs." The README preview says it works with Claude Code, Codex, Cursor and Paseo. The repository is Go and the metadata license is MIT.
Capabilities described
The preview lists these parts: an MV3 Chrome extension that opens agent tabs inactive, with one per Chrome profile; a Go program, "chrome-relay," that runs as a background service and is built and signed on your own Mac; a machine secret stored in ~/.chrome-relay/token and embedded in the URL; a check that the connecting process is an allowed agent app; and selection of which account to use when you have several logins for one site.
Getting started
The preview mentions a build step ("./build") but the supplied data gives no full setup steps. Use the README for installation and security settings.
git clone https://github.com/aindeev/agent-chrome-relay.git
cd agent-chrome-relay
# see README for setupFrequently Asked Questions
Which agents are supported?
The preview says Claude Code, Codex, Cursor and Paseo. It also says only processes from allowed agent apps can connect.
Where is the secret stored?
The preview says it is generated at setup in ~/.chrome-relay/token with mode 600 and embedded in the URL.
What license does it use?
The metadata license field is MIT.