Chrome DevTools MCP: Coding Agents Can Now Debug Live Authenticated Browser Sessions

Google shipped the bridge between terminal agents and visual debugging, and the HN response tells you how badly people wanted it.

Chrome DevTools MCP (requiring Chrome M144 beta) now lets coding agents auto-connect to your running browser session via --autoConnect, including sessions behind sign-in walls and active DevTools debugging panels. Your agent can inspect network requests you've already selected, examine DOM elements, and read console output — all through MCP tool calls from Claude Code, Cursor, or any MCP-compatible client. Chrome shows a permission dialog on each connection and a banner while the session is active. Chrome for Developers

At 522 points and 209 comments on HN, this December 2025 post resurfaced today with massive engagement — a signal that the authenticated-browser-state gap has been a persistent pain point for every web developer trying to use coding agents. The fundamental problem: your terminal agent can read code, run tests, and modify files, but it cannot see what the application actually looks like in the browser. It can't see the CSS that's broken, the network request that's 404ing behind your auth wall, or the console error that only reproduces with your specific session state.

This changes that. The security model is conservative — per-connection permission dialogs, visible session indicator — but the capability is transformative. For web development specifically, this may be the single biggest quality-of-life improvement since agents gained file editing.