Chrome developers can now let coding agents directly connect to active browser sessions through an enhanced Chrome DevTools MCP server. This new capability lets AI assistants reuse existing sessions without requiring additional sign-ins and access active debugging sessions in real-time.

Chrome M144 introduces a remote debugging connection feature that builds on existing Chrome capabilities. By default, remote debugging is disabled and requires explicit user permission through chrome://inspect#remote-debugging. When configured with the --autoConnect option, the MCP server requests debugging access and shows a permission dialog to prevent misuse.

This enhancement bridges manual and AI-assisted debugging workflows. Developers can select network requests or DOM elements in DevTools panels and hand off investigation to coding agents. The team plans to incrementally expose more panel data through the MCP server, making debugging more collaborative between humans and AI tools.