BACK_TO_FEEDAICRIER_2
Chrome DevTools MCP connects agents to live browser sessions
OPEN_SOURCE ↗
HN · HACKER_NEWS// 27d agoPRODUCT UPDATE

Chrome DevTools MCP connects agents to live browser sessions

Google's Chrome DevTools MCP server now lets AI coding agents connect to an already-running, authenticated browser session — not just a fresh isolated tab. Agents can inspect active Elements and Network panels, debug real user state, and investigate issues developers have already surfaced manually.

// ANALYSIS

This is the missing link for AI-assisted debugging — agents can now see exactly what you see, in the exact context where the bug lives.

  • Previous MCP-based browser automation launched fresh sessions, forcing re-authentication and losing state; the `--autoConnect` flag eliminates that friction entirely
  • Works with any MCP-compatible client: Claude Desktop, Cursor, Cline, VS Code Copilot, Gemini CLI — broad ecosystem coverage from day one
  • User permission gate (confirmation dialog + visual banner) is a sensible trust boundary that keeps developers in control while enabling deep agent access
  • Requires Chrome M144+ Beta — early adopter friction, but the npm package (`chrome-devtools-mcp`) is actively maintained at v0.20+
  • Chrome team explicitly plans to "incrementally expose more panel data" — expect Console, Sources, and Performance panels next
// TAGS
chrome-devtools-mcpmcpdevtoolagentbrowser-extensionai-coding

DISCOVERED

27d ago

2026-03-15

PUBLISHED

27d ago

2026-03-15

RELEVANCE

8/ 10

AUTHOR

xnx