Chrome extension
rly — remote browser for AI agents
Install this in the Chrome you want an AI agent to use. One click creates a private session link; paste it into your agent and it can drive this browser. No local install, no admin rights, and it uses the Chrome you already have.
Install from the Chrome Web Store
- Open the Chrome Web Store listing for rly — remote browser for AI agents (link coming soon) and click Add to Chrome.
- Pin the rly icon from the puzzle-piece menu so you can see its status.
- Continue with Start a session.
Manual install (unpacked)
Use this while the store listing is pending, or where the store is blocked but developer mode is allowed.
- Download
rly-extension.zipand extract it to a folder you will keep, for exampleDocuments\rly-extension. Chrome loads the extension from that folder every time it starts. - Open
chrome://extensions(oredge://extensionsin Microsoft Edge). - Turn on Developer mode (top right).
- Click Load unpacked and select the extracted folder, the one that contains
manifest.json. - Pin the rly icon from the puzzle-piece menu.
To update, extract the new zip over the same folder and click the reload icon on the rly card in chrome://extensions. If your organisation blocks developer mode or extensions, use rly-host.exe instead.
Start a session
- Click the rly icon and click Create session. The relay defaults to
https://rly.ems.works; to use your own, change it under Relay settings first. - The popup shows a Session link such as
https://rly.ems.works/mcp/rly_…. Click Copy, or Copy Claude Code command for the readyclaude mcp addcommand. - Paste it into your AI coding agent. For Claude Code:
$ claude mcp add --transport http rly https://rly.ems.works/mcp/rly_… - When you are done, click End session or close the browser.
The agent controls the whole browser: every tab in every normal window, including tabs you open later. chrome:// pages, other extensions' pages and the Chrome Web Store are excluded.
You stay in control
- End at any time. End session in the popup, closing the browser, or clicking Cancel on Chrome's debugging banner ends the session and invalidates its link.
- Visible while active. Chrome shows its “rly started debugging this browser” banner whenever an agent is attached. Tabs the agent opens are kept in a labelled rly agent tab group.
- Treat the link like a password. Anyone with the session URL can drive this browser until the session ends. The token is kept only in session storage and is wiped when the browser closes.
- Not end-to-end encrypted. While a session is active, page content and DevTools traffic pass through and are decrypted by the rly.ems.works gateway, which runs the agent's browser tools. It is not logged or kept after the session. If you need end-to-end encryption, use
rly-hostwithrly pair. See the privacy policy.
Why it asks for these permissions
| Permission | Used for |
|---|---|
debugger | Driving the browser's tabs during a session, using the Chrome DevTools Protocol. |
tabs | Opening, closing and listing the agent's tabs. |
tabGroups | Keeping agent tabs in a labelled “rly agent” group. |
storage | Keeping the session token in session storage (wiped when the browser closes) and the relay setting locally. |
alarms | Keeping the relay connection alive and reconnecting. |
The extension has no content scripts and requests no host permissions.