 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)  José Luis Zapata [GitHub](https://github.com/zapata131) [LinkedIn](https://www.linkedin.com/in/zapata131) [Bluesky](https://bsky.app/profile/zapata131.bsky.social) [Homepage](https://www.zapata131.com)
Published: May 19, 2026
[Video](https://www.youtube.com/watch?v=1AD81ZselPk)
AI coding tools are incredibly powerful at writing code, but they are often
disconnected from its execution. They can generate a complex web app, but they
cannot observe its behavior or inspect its output in a live browser.
[Chrome DevTools for agents](https://developer.chrome.com/docs/devtools/agents) provides your coding agent
with the visibility it needs to verify, debug, and optimize code in real time. A
couple months ago [we showed it for the first time](https://developer.chrome.com/blog/chrome-devtools-mcp),
and now we are excited to announce that Chrome DevTools for agents is now
available as a stable 1.0 release.
## Connect your agent to the browser
Chrome DevTools for agents allows your agent to experience your site like a real
user would. This stable release includes several ways for you and your agent to
interface with Chrome:
- **Model Context Protocol (MCP) server**: A server that connects Large Language Models (LLMs) to DevTools debugging capabilities.
- **Command-line interface (CLI)**: A token-efficient alternative that allows agents to batch actions into scripts.
- **Agent skills**: Expert instructions that teach your agent how and when to use specific tools for tasks like accessibility or performance debugging.
## Debug, emulate, and audit automatically
With the 1.0 release, your coding agent can now perform advanced debugging tasks
that were previously manual.
### Automate quality audits
Your agent can now [run Lighthouse
audits](https://developer.chrome.com/docs/devtools/agents/use-cases/lighthouse-audit) to evaluate website
quality. It can identify issues with accessibility, SEO, best practices, and
agentic browsing. It's like having a linter that understands the runtime. Used
as a quality gate, it turns your coding agent into an expert that catches
critical blockers before they reach production.
### Emulate real-world user experiences
Your agent can use DevTools for agents to test how a site looks and performs on
various devices or in different locations [using emulation
tools](https://developer.chrome.com/docs/devtools/agents/use-cases/emulation). It can resize windows,
simulate geolocations, and throttle network and CPU speeds to mimic real-world
conditions. This way, your agent can test mobile-specific behaviors, like burger
menus, without you having to manually resize your browser.
### Develop and debug Chrome Extensions
You can also let your agent not only help you develop Chrome Extensions but also
debug them. Your agent can install, reload, and trigger extension actions
directly. This helps automate the frequent "save-and-refresh" cycle during
development. It can also dive into background scripts and extension pages to
help you fix bugs in more complex browser setups.
### Debug and test WebMCP tools
We're also bringing deep visibility to the [WebMCP](https://developer.chrome.com/docs/ai/webmcp) (Web Model
Context Protocol) Origin Trial to help you implement this new API.
Instead of having your agent rely on signals to infer a plan for navigating the
DOM, it can directly interact with structured tools that you expose using
WebMCP. This makes it easier to develop, test and debug these tools: your agent
can list, programmatically invoke, and validate their correctness in real time.
This streamlines the process of adding WebMCP support to your site and testing
it.
### Detect and debug memory leaks
We have also added dedicated tools for memory analysis. Your agent can now take
heap snapshots to identify memory leaks, such as detached DOM nodes. By using
specialized memory leak debugging skills, the agent acts as a performance expert
to help you keep your application lean and fast.
### Hand over sessions with auto-connect
You can [share your current browser context with an agent](https://developer.chrome.com/docs/devtools/agents/use-cases/auto-connect),
instead of the agent opening its own sandboxed browser instance (which is how
DevTools for agents usually gives agents access to the browser). This is perfect
for debugging things that require a login, like an authenticated dashboard,
where you want the AI agent to take over the technical investigation without you
having to re-authenticate everything.
### Expose internal state with third-party developer tools
Third-party developer tools allow your web application to share internal state
and component details directly with AI agents. By providing access to data that
is usually hidden from standard analysis, these tools give agents the context
they need to understand complex logic. This results in more accurate debugging
suggestions based on how the application is actually behaving in the browser.
## Get started
You can install the stable release using `npm` or configure it directly in your
agent of choice:
### Antigravity
Chrome DevTools for agents comes pre-bundled with [Antigravity
2.0](https://antigravity.google/). You can start using it immediately with the
*browser sub-agent*. Try using a slash command such as:
/browser Navigate to the Google homepage
To access specialized agent skills, we recommend installing the DevTools plugin
during the **Build with Google** step of the initial setup or within the
application settings. For more information, check out the [Antigravity Browser
Subagent documentation](https://antigravity.google/docs/browser-subagent).
### Gemini CLI
To install the MCP package and skills as an extension, use the following
command:
$ gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp
### Claude Code
To install Chrome DevTools for agents as a Claude Code Plugin, use the following
slash commands in Claude Code. Add the marketplace registry:
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
And install the plugin from the marketplace registry:
/plugin install chrome-devtools-mcp@chrome-devtools-plugins
For more detailed guides and example prompts, visit our [Chrome DevTools for
agents documentation](https://developer.chrome.com/docs/devtools/agents). You can also explore the
[source code on GitHub](https://github.com/ChromeDevTools/chrome-devtools-mcp).