![Matthias Rohmer](https://web.dev/images/authors/mrohmer.jpg) Matthias Rohmer [X](https://twitter.com/matthiasrohmer) [GitHub](https://github.com/matthiasrohmer) [LinkedIn](https://www.linkedin.com/in/matthias-rohmer-b09191b0) [Bluesky](https://bsky.app/profile/matthiasrohmer.bsky.social)

<br />

[Video](https://www.youtube.com/watch?v=2rOeZ98AOb8)

In Chrome 144 the team shipped a highly anticipated feature to the Chrome
DevTools MCP server, the new Request conditions panel and improvements for
debugging fonts and adopted stylesheets..

This concludes the remarkable list of features we shipped throughout 2025. Want
to see if you missed any of them? Then check out the highlights following or browse
through our [past editions of What's new in DevTools.](https://developer.chrome.com/docs/devtools/news)

## DevTools MCP server updates

We landed various fixes for the DevTools MCP server and released v0.12.1. This
version introduces a key new feature, auto connection, which enables you to
**re-use an existing browser session**. With auto connection, you can start
debugging yourself in Chrome, and then point DevTools MCP to the same Chrome
instance to pick up where you left off.

Learn more about auto connection for DevTools MCP [in the related blog post](https://developer.chrome.com/blog/chrome-devtools-mcp-debug-your-browser-session.md.txt).
See the [public changelog on GitHub](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/CHANGELOG.md)
for the full list of changes and bugfixes.

## Individual network request throttling

> [!NOTE]
> This feature was disabled by default in Chrome 144 due to a regression. To enable it for Chrome 144, set the flag `Enable individual request throttling in DevTools` and select *Enable blocking and throttling* checkbox in the *Request Conditions* drawer. The feature will be available again by default in **Chrome 145**.

The Network request blocking panel has been renamed to **Request conditions** .
Alongside blocking requests, this panel now also lets you *throttle*
individual requests.

Open the panel from **⋮** \> **More Tools** \> **Request Conditions** . Toggle
the **Enable blocking and throttling** checkbox to enable request blocking.
Click the **+** button to add a new text pattern. Click the
icon to discard all rules.

Learn how to throttle individual network requests [in the updated docs](https://developer.chrome.com/docs/devtools/network-request-blocking).

## Edit @font-face and @font-feature-values rules

`@font-face` and `@font-feature-values` are now shown in the **Styles** panel
and can be edited from there.

## Adopted stylesheets in the Elements panel

The **Elements** panel now shows adopted stylesheets under shadow roots and
document roots. This makes it easier for those working with constructed
stylesheets to find stylesheets affecting their elements and to debug styles,
especially when they unexpectedly don't apply.

## What was new in DevTools 2025

### AI innovations

Starting with **Console insights** , AI innovations by now have become an
integral part of Chrome DevTools with the **AI assistance** panel being the main
hub for context-aware AI-assisted debugging. With **Code suggestions** in the
Console and Sources panels and auto annotations from Gemini in your Performance
traces, DevTools offers a comprehensive set of AI-powered tools to streamline
your workflows.

- **End-to-end styling fixes:** Ask Gemini to [fix CSS issues](https://developer.chrome.com/blog/new-in-devtools-137.md.txt#ai-styling) and, combined with Workspaces, save those changes directly back to your source files on disk.
- **Ask about performance:** You can now discuss a [full performance trace](https://developer.chrome.com/blog/new-in-devtools-142.md.txt#performance) with AI assistance, or deep-dive into any Performance insight, or use Gemini to [annotate a trace](https://developer.chrome.com/blog/new-in-devtools-137.md.txt#ai-annotations).
- **Visual debugging:** The AI assistance panel became multimodal, letting you [upload images](https://developer.chrome.com/blog/new-in-devtools-139.md.txt#multimodal-input) or [take screenshots](https://developer.chrome.com/blog/new-in-devtools-137.md.txt#ai-screenshot) to help Gemini understand and help you debug visual glitches.

### Performance

We redesigned the **Performance** panel to make performance debugging less
overwhelming and more actionable. For example, a recorded trace now comes with
curated insights that help you identify bottlenecks faster and navigate traces
faster. Other improvements include the following:

- **Actionable insights:** We introduced a robust set of [Performance Insights](https://developer.chrome.com/blog/new-in-devtools-136.md.txt#perf-insights), identifying specific issues like [LCP by phase](https://developer.chrome.com/blog/new-in-devtools-135.md.txt#lcp-field), [Layout shift culprits](https://developer.chrome.com/blog/new-in-devtools-137.md.txt#ai-insights), and [Document request latency](https://developer.chrome.com/blog/new-in-devtools-137.md.txt#ai-insights).
- **Real-world context:** We integrated [Field data](https://developer.chrome.com/blog/new-in-devtools-134.md.txt#field-data) and [CrUX data](https://developer.chrome.com/blog/new-in-devtools-135.md.txt#lcp-field) directly into the Performance panel, allowing you to validate lab results against real user experiences.
- **Framework context:** [Angular v20](https://blog.angular.dev/the-angular-custom-profiling-track-is-now-available-0f9d8d36218a) and [React v19.2](https://react.dev/reference/dev-tools/react-performance-tracks) are now using the [Extensibility API](https://developer.chrome.com/docs/devtools/performance/extension.md.txt). Understanding main thread bottlenecks becomes easier with a direct view of your component tree. Shoutout to our partnership with the Angular and React team!
- **Improved collaboration:** Sharing traces became easier with the ability to annotate traces and options to [export resource content and source maps](https://developer.chrome.com/blog/new-in-devtools-143.md.txt#trace-sharing), ensuring a colleague or your future self have all the context they need.

### Web Platform

DevTools kept pace with the evolving web platform, adding dedicated tooling for
the latest CSS specifications while improving the developer experience for
established features.

We added deep tracing for [complex CSS variable chains](https://developer.chrome.com/blog/new-in-devtools-138.md.txt#debug-css-values), Baseline
availability to property tooltips, and just recently introduced debugging
support for complex entry animations using the [`@starting-style`](https://developer.chrome.com/blog/new-in-devtools-143.md.txt#starting-style) rule and a
visual editor for the new [`display: masonry`](https://developer.chrome.com/blog/new-in-devtools-141.md.txt#masonry) layout.

## Download the preview channels

Consider using the Chrome [Canary](https://www.google.com/chrome/canary/), [Dev](https://www.google.com/chrome/dev/), or [Beta](https://www.google.com/chrome/beta/) as your default development browser. These preview channels give you access to the latest DevTools features, let you test cutting-edge web platform APIs, and help you find issues on your site before your users do!

## Get in touch with the Chrome DevTools team

Use the following options to discuss the new features, updates, or anything else related to DevTools.

- Submit feedback and feature requests to us at [crbug.com](https://crbug.com).
- Report a DevTools issue using the **More options** \> **Help** \> **Report a DevTools issue** in DevTools.
- Tweet at [@ChromeDevTools](https://twitter.com/intent/tweet?text=@ChromeDevTools).
- Leave comments on [What's new in DevTools YouTube videos](https://goo.gle/devtools-youtube) or [DevTools Tips YouTube videos](https://goo.gle/devtools-tips).