GoKawiilSebastian Benz Alex Rudenko
We shipped an enhancement to the Chrome DevTools MCP server that many of our users have been asking for: the ability for coding agents to directly connect to active browser sessions.
With this enhancement, coding agents are able to:
Re-use an existing browser session: Imagine you want your coding agent to fix an issue that is gated behind a sign-in. Your coding agent can now directly access your current browsing session not requiring an additional sign-in. Access active debugging sessions: Coding agents can now access an active debugging session in the DevTools UI. For example, when you discover a failing network request in the Chrome DevTools network panel, select the request and ask your coding agent to investigate it. The same also works with elements selected in the Elements panel. We are excited about this new ability to seamlessly transition between manual and AI-assisted debugging.
See it in action:
The auto connection feature is an addition to the existing ways for the Chrome DevTools MCP to connect to a Chrome instance. Note that you can still:
Run Chrome with a Chrome DevTools MCP server-specific user profile (current default).
Connect to a running Chrome instance with a remote debug port.
Run multiple Chrome instances in isolation with each instance running in a temporary profile.
How it works
... continue reading