# Chrome Extension > "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. - Area: Desktop, mobile and web - Plans: All plans - Last checked against the product: 2026-09-30 - Web page: https://agentsroom.dev/docs/chrome-extension ## 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); and you send the whole page's HTML straight into the composer of the agent you are working with on the desktop. 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 desktop composer: the **HTML capture (Chrome extension)** button opens a short popover with "Get the Chrome extension"; also on the site pages Figma to AI Agents and Public Backlog). - 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)](https://agentsroom.dev/docs/chrome-control.md)), **Agents** (send the page to the active agent of your desktop) 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: **; 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 1. 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. "Remember password on this device" is optional and meant for your own machine only. 2. **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. 3. **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**. 4. **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. 5. 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. - `composerHiddenActions` (global, Settings > Composer > Composer toolbar buttons): hide the **HTML capture (Chrome extension)** button if you do not use it. ## 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, the agent that picks them up can run on any CLI. ## 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" requires the desktop app running on the same computer and grants the extension a one-time loopback permission on first use. - 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 - **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. ## Related - [Public Remote Backlog](https://agentsroom.dev/docs/public-backlog.md): the portal the extension posts to. - [Figma to AI Agents](https://agentsroom.dev/docs/figma-to-ai-agents.md): the Figma capture workflow. - [Backlog Task Board](https://agentsroom.dev/docs/backlog-task-board.md): where the tickets land and start agents. - [AgentsRoom in Chrome (agents drive your own Chrome)](https://agentsroom.dev/docs/chrome-control.md): the same extension lets your agents DRIVE this Chrome (AgentsRoom in Chrome). - [Browser Automation](https://agentsroom.dev/docs/browser-automation.md): point changes in the embedded browser instead. - [Account Sign-In](https://agentsroom.dev/docs/account-sign-in.md): the account the extension signs in to, and its other doors.