Chrome listed online but the agent cannot reach it
- Desktop, mobile and web
- All plans
What it does
A Chrome shows as online as long as its extension keeps announcing itself, but Chrome can put the extension to sleep between two announcements. Before each action, AgentsRoom now checks that the extension of the Chrome the agent drives really answers. When it has been silent, AgentsRoom asks it to reconnect and waits up to 20 s, then runs the action. When it still cannot reach it, the agent gets the real reason and what to click, instead of a raw timeout.
Where to find it
Nothing to turn on: it runs before every chrome_* action. The agent can also test the connection on demand (see
Agent tools below).
How to use it
- If an agent says the extension "did not answer", click the AgentsRoom icon in that Chrome's toolbar: opening the popup wakes the extension. Then ask the agent to try again.
- If the agent says "this computer cannot reach the AgentsRoom relay", check this computer's network, VPN or proxy. When Chrome runs on the same computer, "Connect directly" in the extension popup (Browser tab) avoids the relay.
- If that Chrome runs on another computer, check that computer is awake and Chrome is open.
Settings
None.
Agent tools (MCP)
chrome_list_browsers: shows, per Chrome, what its session saw lately ("relay connected, extension last answered 12 s ago").chrome_list_browserswithcheck: true: tests the Chrome the agent drives right now (wakes its extension, up to 20 s) and says what is wrong, or that it answers and by which route.
Providers
All providers: the Chrome tools are an MCP server, the same for every agent CLI.
Mobile
Not on the phone (no browser surface there). An agent launched from the phone gets the same checks.
Limits
- A Chrome action that still gets no answer is never replayed by AgentsRoom: it may already have happened in the tab.
- An older extension works too (it answers the check with "unknown op", which is enough to prove it is there).
Common questions
- My Chrome is listed online, but the agent gets "Chrome is not reachable through the relay" or "bridge rpc timeout after 30000ms". Fixed on 2026-11-10: the first action after choosing a Chrome now waits for the connection, a silent extension is woken up before the action, and a slow page load no longer turns into a timeout. If it still fails, the agent tells you whether the relay or the extension is the problem, and what to click.
- How do I know whether the extension is awake? Ask the agent to run
chrome_list_browserswithcheck: true.
Related
AgentsRoom in Chrome (agents drive your own Chrome), Direct connection between Chrome and the desktop, Chrome Extension