Release / / with chrome-devtools-mcp-v1.10.0
Chrome DevTools for agents chrome-devtools-mcp-v1.10.1
Inspect which CSS rules apply to an element and why.
Before you upgrade to chrome-devtools-mcp-v1.10.1
Console retention is capped at 10,000 messages per navigation; same-document navigation now preserves console history.
Behavior changedInspect browser console messages to diagnose page errors.Inferred
Read the evidence
Puppeteer logs are no longer written to a file unless requested.
Behavior changed
Read the evidence
What changed in chrome-devtools-mcp-v1.10.1
`get_css_styles` returns matched, inline and inherited rules with cascade information; JSON configuration files are supported.
Install [email protected] from npm; requires Node.js and Chrome. Optional tools may require flags.
New things you can do
Available in this release.
AddedInspect matched CSS rules and cascade information for a page element.
Read the evidence
Available in this release.
AddedLoad browser-tool settings from a JSON configuration file.
Read the evidence
Fixed and improved
Explicit false options passed during CLI start are forwarded to the server.
Now worksAutomate and inspect Chrome from the command line without an MCP client.
Read the evidence
Input actions handle JavaScript dialogs that open while the action runs.
Now worksClick, fill forms, drag elements, handle dialogs and upload files in Chrome.
Read the evidence
Lighthouse uses the emulated user agent and final displayed URL.
Now worksRun Lighthouse audits for accessibility, best practices and SEO.
Read the evidence
Seeded by 
@iluxav with Codex, from the release's public sources. Each change links to its evidence.