AgentsRoom in Chrome (agents drive your own Chrome)
- Desktop, mobile and web
- All plans
What it does
Your agents drive the real Google Chrome on your computer, with your own logins, cookies and extensions, through the free "AgentsRoom.dev : AI Dev Remote Control (Chrome companion)" Chrome extension. It is AgentsRoom's alternative to Claude in Chrome, with three differences: every Chrome profile becomes its own named browser ("Chrome · Pro", "Chrome · Perso"), so one agent can work on your professional account while another uses your personal one; the Chrome can sit on another machine of your account, the traffic travelling end-to-end encrypted through the AgentsRoom relay; and it works with every agent CLI (Claude Code, Codex, Gemini, Cursor...), because it is an MCP server, not a Claude feature. On the same computer they connect directly, even on a network that blocks AgentsRoom: Direct connection between Chrome and the desktop.
It is separate from the AgentsRoom browser, the Chromium screen embedded in the desktop's right panel: that one is a separate per-project session, shared by the agents of that project; this one is YOUR Chrome. The two never mix: different MCP server, different tools, different capability on the agent.
Where to find it
- Chrome: the AgentsRoom extension popup, Browser tab (first tab). The switch "Let my agents drive this browser" is on by default; the "Browser name" field names this profile for your agents.
- Desktop: right panel > Tests > the Chrome pill (tagged "Extension", next to Browser, tagged "Built-in", and Electron). It opens the "AgentsRoom in Chrome" surface: Connected browsers (name, platform, Online / Offline, or "No Chrome connected" with Get the extension), Token saver (Beta), Agents allowed in Chrome, and Navigation cost (24 h) split between Token saver and Classic.
- Status bar > Chrome chip: tokens Chrome put into your open sessions. Popover: Settings (Token saver, "All extension settings"), Usage in open sessions (per provider: tokens, share, estimated cost), "What the extension does" (folded), Your Chrome profiles (see Which Chrome your agents drive (default Chrome per computer)).
- Settings > Chrome extension: Token saver and "Auto-switch project by URL".
- Agent: Edit agent > Capabilities > AgentsRoom in Chrome (extension), checked by default.
How to use it
- Install the AgentsRoom Chrome extension and sign in with the same account as the desktop. The popup's Browser tab reads "Connecting to AgentsRoom", then "Waiting for a desktop signed in as <email>" (the AgentsRoom account this profile is signed in to) once the relay answers, then "Driven by <device>" when a desktop of your account sees it; "Off. Agents cannot use this browser." when the switch is off. "Cannot reach AgentsRoom from this browser: check its network, proxy or policies" (in orange) means this profile never reached AgentsRoom, so no desktop can list it.
- Name the browser in the popup if you run several Chrome profiles: one name per profile ("Pro", "Personal", "Client").
- Ask any agent, in plain language: "open my Gmail in Chrome and check the last
invoice". The agent calls
chrome_list_browsers, picks the browser withchrome_select_browser(automatic in most cases, see Which Chrome your agents drive (default Chrome per computer)), thenchrome_navigate,chrome_click,chrome_type,chrome_screenshot... - Chrome shows its yellow "AgentsRoom started debugging this browser" banner while an agent drives it. Each agent gets its own tab in an AgentsRoom tab group, never the one you are reading nor another agent's.
The first driving action of a session asks you to allow it (the same Ask before test tools setting as the embedded browser); listing browsers, selecting one, screenshots, waiting, reading state and logs never ask.
Settings
- Token saver (BETA), global setting
browserTokenSaver, off by default: Tests > Chrome > Token saver switch, or the same row in the status-bar Chrome popover (alsosettings_set). Agents started after the change getchrome_read_page/chrome_get_text(andbrowser_read_page/browser_get_texton the AgentsRoom browser), element refs, and no screenshot after an action unless it fails. The desktop decides; each Chrome can turn it off for itself in the extension popup, Browser tab, Token saver switch (on by default, it only follows the desktop). Such a Chrome shows Saver off in the connected browsers list. - Extension popup > Browser tab: "Let my agents drive this browser" (on by default, per Chrome profile) and "Browser name".
- Agent capability
chromeAccess(Edit agent > Capabilities > AgentsRoom in Chrome; alsoagents_save): on by default, uncheck to keep one agent out of your Chrome. Claude in Chrome follows it until set: Claude in Chrome per agent (apart from the AgentsRoom extension). newAgentChromeAccess(Settings > AI providers > "New agents: AgentsRoom in Chrome (extension)", on by default, synced with your account): off = new agents (Add agent on desktop and phone, quick agents, direct catalog suggestions and advisor additions, the project's default agent, the Git Expert, agents started by another agent throughagents_spawnor saved withagents_savewithout an explicit value) start unchecked. Duplicates, templates, team steps and agent profiles keep their own value. A project overrides it in Project settings > Capabilities.- Feature flag
chromeControl(Chrome control in beta features): gates the desktop UI, the MCP server and the site page; on by default since 2026-09-21.
Agent tools (MCP)
Server AgentsRoom-Chrome (installed as soon as one agent has the capability): chrome_list_browsers, chrome_select_browser, chrome_navigate, chrome_click, chrome_type, chrome_scroll, chrome_press_key, chrome_drag, chrome_screenshot, chrome_evaluate,
chrome_wait_for, chrome_get_state, chrome_get_logs, chrome_set_viewport, chrome_go_back, chrome_go_forward,
chrome_reload, chrome_usage (what browsing cost: this session, this agent or everyone), chrome_upload_file
(attach local files by path to a file field, text box or drop zone, 10 files and 6 MB per call).
With the token saver (beta) on, also chrome_read_page (outline of what the agent can click, with refs ar1, ar2...
that chrome_click / chrome_type / chrome_wait_for accept instead of a CSS selector) and chrome_get_text (readable
text, capped), and every action takes screenshot: "off" | "auto" | "on" ("auto" by default: a capture only when the
action failed).
Iframes, cross-origin ones included: chrome_get_state lists them as f1, f2..., chrome_read_page reads them
(refs such as f1:ar10003), and the action tools take frame: "f1". chrome_click also takes trusted: true and
x / y, a real click at a point of the screenshot that reaches whatever is there (then chrome_type with
trusted: true and no selector types into the focused field).
chrome_scroll (real mouse wheel), chrome_press_key (Escape, arrows, PageDown, Ctrl+A, Shift+Tab, on the focused element) and chrome_drag (real press, moves, release) also aim at points of the screenshot and need no selector: what a canvas app (Compose Multiplatform, Flutter Web) or an iframe that cannot be opened requires. They need an up-to-date extension; an older one answers "needs a newer AgentsRoom Chrome extension".
The embedded browser keeps its own AgentsRoom-Browser server (browser_*).
Providers
All providers, no difference: an MCP server declared in the project for every CLI.
Mobile
Not on the mobile companion: the phone has no browser to drive. An agent launched from the phone has the same tools as one launched from the desktop.
Limits
- Token saver (beta): the outline enters open shadow DOM and iframes (cross-origin ones included); judging a visual, a canvas or a chart still takes a screenshot.
- Iframes need the extension version that carries them (an older one answers "update the extension"). Chrome refuses to open an iframe while the tab holds another extension's page (a password manager's menu, for example): that iframe is reported as not read, and a click at x / y still reaches it.
- Needs the extension version that carries the driver, installed from the Chrome Web Store, and the
debuggerpermission it declares (Chrome asks once at install or update). - A browser whose extension Chrome put to sleep is reconnected on its own; one silent for 90 s shows as offline.
Common questions
Can new agents start without Chrome access? Yes: turn off newAgentChromeAccess (see Settings above).
Can an agent attach a file (an image to a post) in my Chrome? Yes, chrome_upload_file: the file is read on the
agent's machine and never enters its conversation.
-
Can the agent act inside an iframe (Google Ads Data Manager, a payment form, an embedded editor)? Yes, cross-origin ones included: by ref (
f1:ar10003) or withframe: "f1", else by clicking a point of the screenshot. Update the extension if the agent says it needs a newer one. -
My Codex agents died at launch on "url is not supported for stdio" with Chrome access on. Fixed on 2026-10-29: the Chrome tool server was described in two places and another agent could rewrite the wrong one first. Only the launch line carries it now, which also gives Chrome to Codex agents started from the phone (a
codex resumetyped by hand in a terminal still has none). -
How many tokens does a Chrome navigation cost? A screenshot is about 1 400 to 1 800 tokens; with the token saver an action costs a few hundred (the page outline). Tests > Chrome > Navigation cost (24 h) shows the estimate for your agents, whatever their CLI, the footer Chrome chip and its Usage section show it for the open sessions, an agent can answer with
chrome_usage, and the Browser trace shows it per call. For Claude and Codex, Session info > Tool usage shows the billed tokens each tool added to the context. -
I have two Chrome profiles with the extension, but my agents only see one. Open the extension popup of the missing profile, Browser tab. "Waiting for a desktop signed in as <email>" with an email that is not the desktop's: that profile is signed in to another AgentsRoom account ("Continue with Google" uses that profile's own Google account, and a browser is only listed to the desktops of its account): sign the extension out and back in with the desktop's account. "Cannot reach AgentsRoom from this browser": that profile's network, proxy or policies block AgentsRoom. "Off": turn on "Let my agents drive this browser". No popup at all: the extension is turned off in chrome://extensions (Chrome does that after an update until its new permission is accepted). The profile must also be open: a closed Chrome profile does not run its extension.
-
Can agents stop sending screenshots all the time? Yes: turn on Token saver (beta) in Tests > Chrome. The agent reads the page instead, and still asks for a screenshot to judge a visual (layout, a chart, a canvas).
-
Is there an alternative to Claude in Chrome? Yes: this. Same idea, but every Chrome profile is a named browser, the Chrome can be on another machine, and it works with every agent CLI, not only Claude.
-
Does the agent see my passwords? It sees what the page shows, like you. Nothing is stored by AgentsRoom and the relay only carries encrypted blobs. Uncheck "AgentsRoom in Chrome" on agents that should never touch your Chrome.
-
Every time my agent comes back to Chrome it opens a new tab instead of reusing its page. Fixed in the extension (2026-10-05 and 2026-10-06): an agent takes back the tab it left, as long as that tab is still open and still in the AgentsRoom group (a tab you dragged out of the group is yours), even after a pause or a Chrome restart of the extension, and two simultaneous calls no longer open two tabs. Update the extension. A tab Chrome refuses to re-attach (another extension's page or frame) is still replaced by a new one.
-
Why does the agent say it only has the embedded browser? Its session started before the extension was connected, or the agent's capability is unchecked: restart the agent after connecting the extension.
-
My agent gets "Cannot access a chrome-extension:// URL of different extension" or another agent's page. Another extension's page or frame (password manager, tab suspender) blocks its tab. Update the extension and the desktop: each agent gets its own tab, and a blocked tab is replaced.
Related
- Chrome Extension: the extension that carries the driver (tickets, send page, point on page).
- Browser Automation: the embedded AgentsRoom browser, the other surface.
- Agent Delegation: the QA Bot can drive Chrome the same way.
- Remote Fleet: the relay rooms this feature reuses across machines.
- Which Chrome your agents drive (default Chrome per computer): which Chrome an agent drives, the Default checkbox.