Chrome Extension
- Desktop, mobile and web
- All plans
What it does
"AgentsRoom.dev : AI Dev Remote Control (Chrome companion)" is a free Chrome extension that turns any web page into an entry point for your agents. From its popup you file a bug, a feature or a question into a project backlog, with the selected text quoted and an optional screenshot; you point at an element of the page and describe a change (the ticket carries the element's HTML, a CSS selector and the URL); you send the whole page's HTML straight into the composer of the agent you are working with on the desktop; and you report a bug directly to that agent, with a screenshot of the tab, without copying a file path. A Figma frame goes through the same ticket form, as a screenshot you attach yourself: the extension has no Figma integration and reads no CSS or design token. Anyone can use it against a public backlog without an account.
Where to find it
- Install from the Chrome Web Store (link in the Chrome chip of the desktop status bar, and on the site pages Figma to AI Agents and Public Backlog). The composer no longer has an HTML capture button (removed 2026-10-26 to lighten the toolbar): a page sent from the extension still lands in the composer.
- Click the AgentsRoom icon in the Chrome toolbar to open the popup. Its current version (the one that also carries the browser driver) has three tabs: Browser (let your agents drive this Chrome, see AgentsRoom in Chrome (agents drive your own Chrome)), Agents (report a bug to the active agent of your desktop, or send it the page) and Backlog (file a ticket); a Switch theme button in its header toggles light and dark.
- Desktop side: Project settings > Chrome Extension (auto-selection by URL).
- Desktop status bar: the Chrome button opens a window with the connection state (Connected / Not connected), the settings, Your Chrome profiles (when Chrome control is available: every Chrome profile that ever connected to this computer, connected ones first with a green dot, the others by Last connected: <date>; an offline profile can be removed with the bin icon then Remove; the list stays on this computer), and the install link Get the Chrome extension.
How to use it
- Sign in with your AgentsRoom account (email and password, Continue with Apple or Continue with Google), or enter a public backlog slug to post anonymously, or, with no account or on a network that blocks sign-in, click Connect to AgentsRoom on this computer and approve in AgentsRoom: Browser and Agents then work over the loopback, with no server, and Disconnect replaces Sign out. "Remember password on this device" is optional and meant for your own machine only.
- File a ticket (Backlog tab): pick the project (My projects / Shared with me / Joined), type the title and description, attach a screenshot (PNG, JPG or WEBP up to 4 MB), submit. Join a project you were invited to adds a public or unlisted slug to the list.
- Point on page (signed in): hover an element, click to pin it, write the comment in the bubble. The title is generated for you and the ticket goes to the backlog's default agent when one is configured in Share backlog.
- Send page to my desktop (Agents tab, signed in, desktop open on the same machine): the page's HTML lands as an attachment in the composer of your active agent, over the local loopback, never through a server.
- Report a bug to my agent (Agents tab, signed in, desktop open on the same machine): write what is wrong, keep Include a screenshot of this tab checked, click Send to my agent. The message leaves right away, as if typed in the composer of your active agent, with the page's URL and the path of the screenshot; the badge at the top of the tab names that agent, and the button says where the report went. If the agent cannot take it yet (still starting, or its CLI is showing a question), it waits in that agent's queue and leaves on its own. Your words stay in the popup until they are sent.
- Figma: screenshot the frame, then attach that image with your brief through the ticket form; it becomes a ticket an agent picks up from the board. Point on page has nothing to grab inside the Figma canvas (WebGL, no DOM), so it stays for your own running app.
The extension remembers the last project you picked; a project whose Associated URLs match the current page is preselected.
Settings
- Project settings > Chrome Extension > Auto-select this project by URL and Associated URLs: when one of these URLs is open in Chrome, the extension switches to this project automatically.
chromeUrlAutoSwitchEnabled(global): switch the active project automatically when Chrome navigates to one of a project's associated URLs.
Agent tools (MCP)
None directly. Tickets filed by the extension are ordinary backlog tickets, readable through backlog_list / backlog_get.
Providers
All providers, no difference: the extension writes tickets and composer attachments, and a bug report takes the path of a message typed in the composer, so it reaches any CLI (Claude Code, Codex, Antigravity, Cursor and the others). Whether the agent sees the screenshot as an image depends on the CLI and its model; every one receives its path.
Mobile
Not applicable: the extension runs in desktop Chrome. Tickets it files appear on the phone's backlog like any other.
Limits
- Chrome (Manifest V3) only; no Firefox or Safari build.
- "Send page to my desktop" and "Report a bug to my agent" require the desktop app running on the same computer and grant the extension a one-time loopback permission on first use.
- A bug report goes to the agent in front of you in the desktop. The assistant, a remote agent and the AI Suggestion screen get it in their message box instead: you review it and press Send.
- The desktop's loopback port answers the extension and local tools only: since 2026-11-03 a web page you visit can no longer ask it which project and agent a bug report would go to.
- The project list is the union of the projects seen by every desktop signed in to your account; a project deleted on one machine can keep appearing until no machine pushes it any more.
- Free plan backlog quotas apply to the tickets it files (one remote backlog, 50 tickets per month).
- The remembered password is stored by Chrome for that extension, not encrypted at rest: leave the box unticked on a shared computer.
Common questions
- A row of "AgentsRoom" chips piled up in my bookmarks bar. Chrome saves and syncs a tab group when its last tab is closed, so every test added one chip per computer. Fixed on 2026-11-02, once the extension is updated: AgentsRoom takes the last tab out of the group before closing it. Remove existing chips by hand (right-click, Delete group); the removal syncs. A group still open when Chrome quits, or closed by hand, stays saved.
- Do I need an account? No for a public backlog slug. Yes for your own projects, Point on page and Send page to my desktop.
- Where does the ticket go? Into the backlog of the project you picked; with Point on page, to that backlog's default agent when one is set.
- The dropdown shows "Project abc123" instead of a name. The project was opened on a desktop before names were synced; it gets its name the next time that desktop starts signed in.
- My popup has no Browser tab, and my agents say no Chrome is connected. Your copy of the extension predates Chrome control (1.183.0). Update it from
chrome://extensions(Developer mode > Update), then switch it back on if Chrome disabled it to ask for the new debugger permission. Since 1.187.0 the agents themselves give you these steps when they find no connected Chrome. - A day after signing in, my agents said "No Chrome is connected" and every Chrome of my account vanished at once. Fixed on 2026-09-29: the extension used to drop its sign-in when the 24-hour session expired instead of renewing it. It now renews the session on its own and only signs out if that fails. A session opened before the fix cannot renew: sign in to the extension one last time.
- Which tabs is my agent using? The ones in the dark grey tab group named AgentsRoom with a robot icon (it was orange before 2026-09-24). Closing the group closes them all.
- Where do I see which Chrome profiles are linked to this computer? Status bar > Chrome > Your Chrome profiles, with the last connection of each.
- Does the page HTML go through AgentsRoom servers? No, it travels on your machine's loopback from Chrome to the desktop app. The same goes for a bug report and its screenshot.
- I captured a bug in Chrome and my agent heard nothing about it. A ticket from the Backlog tab waits on the board until an agent picks it up, and Send page or Point on page only fill the agent's message box. To tell the agent now, use Report a bug to my agent in the Agents tab: it sends the message for you, on any CLI.
- My agent says "refused: this call names an agent other than the one running in the console". On Windows, an agent could be mistaken for one whose console had just closed, and every mailbox tool was then refused. Fixed in the version that ships this form. If you still see it, restart that agent from AgentsRoom.
Related
- Public Remote Backlog: the portal the extension posts to.
- Figma to AI Agents: the Figma capture workflow.
- Backlog Task Board: where the tickets land and start agents.
- AgentsRoom in Chrome (agents drive your own Chrome): the same extension lets your agents DRIVE this Chrome (AgentsRoom in Chrome).
- Browser Automation: point changes in the embedded browser instead.
- Account Sign-In: the account the extension signs in to, and its other doors.