Chrome 150, released June 30, 2026, brings a set of DevTools updates focused heavily on debugging support for AI coding agents alongside more traditional developer-facing improvements. Google's Chrome for Developers blog detailed the changes in its regular "What's new in DevTools" post.

The most substantial addition is a new memory debugging suite, enabled through an experimental flag, that lets an agent or a developer capture and analyze V8 heap snapshots directly to diagnose JavaScript memory leaks and unexpected object retention. Chrome has been building out DevTools features specifically for coding agents for several releases now, giving tools that operate a browser programmatically the same console logs, network traffic, and diagnostic surfaces a human developer would use manually.

The AI assistance panel built into DevTools also expanded, adding nine new widgets that surface data from the Lighthouse, Network, Sources, and Performance panels directly inside the assistant's interface. The stated goal is giving developers more visibility into what data the assistant is actually pulling from when it answers a question or suggests a fix, rather than treating its reasoning as a black box.

On the more conventional side, Chrome 150 adds direct in-place editing for CSS @container rules, letting developers modify container names and query conditions without leaving the Styles pane, along with new authoring support for the newer @function and @counter-style at-rules.

None of these features require any migration work from existing DevTools users -- they're additive tooling available the next time Chrome updates. The agent-focused features are opt-in behind experimental flags for now, consistent with how Chrome has rolled out its previous rounds of agent-oriented DevTools capabilities before stabilizing them in later releases.

Source: Chrome for Developers — What's new in DevTools (Chrome 150)