Your agent, driving the browser where your work actually lives.
rly connects Claude Code, Codex or any MCP client on your machine to Chrome inside a VM, a Citrix session or a locked-down company laptop. Both ends dial out, so there are no inbound ports, no VPN and no admin rights. One pairing code, then end-to-end encryption.
Works with Claude Code · Codex · Cursor · any MCP client
$ rly pair 4821-acid-mango-rift --name vm1
paired with vm1 · keys pinned
$ claude mcp add vm-browser -- rly mcp --peer vm1
$ claude
› open the expense portal in the VM and
download last month's statement
● browser_navigate intranet.corp/expenses
● browser_click "Statements"
✓ saved statement-2026-10.pdf
Why rly
The apps your agent needs are behind someone else's firewall
Internal portals, browser-based ERP screens, client tenants and SSO-only SaaS are only reachable from a specific machine. rly puts your local agent's hands on that machine's browser without moving your agent, your keys or your prompts there.
Citrix & VDI
Run the extension or a single user-mode exe inside the virtual desktop. Your agent stays on your laptop and drives the browser in the session.
Locked-down laptops
No admin rights, no service, no driver, no inbound ports. Outbound HTTPS on 443 is all it needs, including through corporate proxies.
Intranet & SSO apps
The remote browser is already signed in. Your agent gets the full Playwright toolset (navigate, click, fill, snapshot, screenshot) on pages it could never reach directly.
How it works
Three pieces, one encrypted tunnel
Nothing in the VM runs agent logic. The VM side only forwards raw Chrome DevTools Protocol (CDP).
The agent tools run locally in @playwright/mcp, connected to a CDP endpoint that rly exposes on 127.0.0.1.
- Pair once. The VM side shows a short code such as
4821-acid-mango-rift. Type it on your machine. Both sides then pin each other's public key. - Connect. Both ends dial out to the relay over WSS and run an authenticated Noise handshake. They reconnect automatically.
- Drive.
rly mcpstarts@playwright/mcpagainst the tunnel. Your agent navigates, clicks, fills forms and takes snapshots in the remote browser.
Security
Built so the relay can't read your browser
The relay is a dumb pipe by design. Keys exist only on your two paired devices. The relay never has them,
so it cannot decrypt traffic, even if it is compromised. This applies to rly-host + rly.
Chrome extension sessions are different: their hosted MCP link is served by the rly.ems.works gateway, which
decrypts session traffic while a session is active (details).
SPAKE2 pairing code
A one-time code with about 31 bits of entropy (a 4-digit nameplate plus three words) runs a password-authenticated key exchange. An attacker gets one online guess before the relay retires the nameplate, and a wrong code fails loudly on both sides. Codes expire after 10 minutes.
Noise KK sessions
Each connection runs Noise_KK_25519_ChaChaPoly_BLAKE2s with the static keys pinned at pairing. That gives mutual authentication and forward secrecy in one round trip. If a key doesn't match, the session is rejected.
The relay sees only ciphertext
The relay sees IP addresses, timing, byte counts and a random routing id. It never sees URLs, page content, cookies or keystrokes. It keeps state in memory only and never logs payloads.
No admin rights on the VM
Use a browser extension or a single user-mode exe. Nothing to install as a service, no inbound ports, no driver. The only traffic is outbound HTTPS on port 443, and HTTP CONNECT proxies are supported. The browser runs in a dedicated profile.
Quickstart
Up and running in two minutes
With the Chrome extension, create a session and paste its link into your agent; that's all. With rly-host, the VM shows you a pairing code: pair your own machine with it and register the MCP server with your agent.
1 · In the browser the agent should use: pick one
Chrome extension
- Install rly — remote browser for AI agents from the Chrome Web Store, or load it unpacked.
- Click the rly icon and choose Create session. The relay defaults to
https://rly.ems.works. - Click Copy setup for your agent and paste it into any MCP-capable agent; it adds the server itself. Or copy the MCP URL and add it as a remote HTTP server. Nothing to install on your machine; skip part 2.
- Click End session or close the browser to stop.
Uses the browser that's already there. No exe, no admin rights. The agent controls every tab in the browser (except chrome://, extension and Web Store pages), and Chrome shows a “rly started debugging this browser” banner while it is attached. Extension sessions are not end-to-end encrypted: the rly.ems.works gateway decrypts traffic while a session is active. Details.
rly-host.exe
- Download
rly-host-windows-x86_64.exe(or the Linux/macOS build). - Pair it, then keep it running:
> rly-host pair --relay https://rly.ems.works --name vm1
Pairing code: 4821-acid-mango-rift
> rly-host run
Starts Chrome or Edge with its own profile. Behind a proxy, add --proxy http://proxy:8080 or set HTTPS_PROXY.
2 · On your machine (rly-host only)
For rly-host: install rly and Node.js 18+ (used for npx @playwright/mcp). Then pair, using the code from the VM:
$ rly pair 4821-acid-mango-rift --relay https://rly.ems.works --name vm1
paired with vm1
$ claude mcp add vm-browser -- rly mcp --peer vm1
Then ask Claude Code something like “open example.com in the VM browser and tell me the title.” Other MCP clients can use rly mcp --peer vm1 as a stdio server command. For raw CDP (Playwright or Puppeteer scripts), run rly cdp --peer vm1 --port 9222.
Downloads
Single static binaries
No installer and no runtime dependencies. Put the binary anywhere on your PATH. On macOS and Linux, run chmod +x first.
| Component | Runs on | Windows x86_64 | Linux x86_64 | macOS Apple silicon |
|---|---|---|---|---|
| rly local CDP proxy + MCP launcher |
Your machine | rly-windows-x86_64.exe |
rly-linux-x86_64 |
rly-macos-aarch64 |
| rly-host VM side, launches the browser |
Remote VM | rly-host-windows-x86_64.exe |
rly-host-linux-x86_64 |
rly-host-macos-aarch64 |
| rly extension one-click sessions, no local install |
Any Chrome | rly-extension.zip (unpacked install, instructions), or the Chrome Web Store |
||
| rly-relay self-host your own relay |
Linux server | n/a | rly-relay-linux-x86_64 |
n/a |
FAQ
Common questions
Can the relay read what my agent does?
Not with rly-host + rly: traffic is encrypted end to end with keys that exist only on your two paired devices. Chrome extension sessions are the exception; their hosted MCP link is decrypted by the rly.ems.works gateway while a session is active. See privacy.
Does my agent run in the VM?
No. The agent, its prompts and its tools stay on your machine. The remote side only forwards Chrome DevTools Protocol to its local browser.
Which browsers are supported?
Chrome and Edge (any Chromium browser with CDP). The extension works in Chrome; rly-host launches Chrome or Edge with its own profile.
Can I run my own relay?
Yes. rly-relay is a single Linux binary. Point both ends at it with --relay https://your-host.
How do I stop the agent's access?
End the extension session or close the browser. For rly-host, stop the process, or remove the pairing with rly-host unpair <name>.
Give your agent a browser in the right place.
Install the extension and paste one link into your agent. Two minutes, no admin rights.