Chrome's "New in DevTools" roundup for November 2026 buried its most consequential change under a subhead most developers skimmed past: DevTools for Agents. Alongside the visual position-area editor that grabbed attention this week, Chrome DevTools MCP — the open-source server that connects AI coding assistants to a running Chrome instance — shipped a get_css_styles tool that exposes computed and matched CSS the same way a human inspecting an element in the Styles pane would see it, just structured for a model to parse. Independent coverage and the project's own GitHub pull requests confirm the same scope: pagination support, formatted matched rules, inherited rules, pseudo-elements, @keyframes, and at-rules like @position-try and @property. For teams already running agentic coding workflows, this closes a gap that made CSS specifically hard for an agent to debug well: it could read your stylesheet source, but it couldn't see what the browser actually computed after the cascade, inheritance, and specificity did their work — which is exactly where most real CSS bugs live. That gap between "what you wrote" and "what the browser decided" is also where AI agent integration work tends to get harder than a demo suggests, because an agent that can't see ground truth will confidently propose a fix for the wrong rule.
What the tool actually exposes
The get_css_styles tool returns the same layered picture a human gets by opening the Elements panel and scrolling the Styles pane, but as structured output an agent can reason over without screen-scraping: matched rules in cascade order, inherited rules from ancestor elements, pseudo-element styles (::before, ::after, and friends), active @keyframes definitions, and at-rules including @position-try and @property. It supports pagination through pageSize and pageIdx parameters rather than dumping every matching rule into a single response — a deliberate design choice for elements buried under dozens of overriding declarations, where an unpaginated dump would blow past a model's useful context before it ever reached the rule that mattered. Google highlighted the tool publicly in late October as part of the Chrome DevTools MCP server, and the Chrome team's own "New in DevTools" post folds it into the broader November 2026 release alongside the visual anchor-positioning editor — two different audiences (a developer clicking in the UI, an agent calling a tool) getting equivalent access to the same underlying style-computation engine.
Why "what the browser computed" is the hard part
Reading a stylesheet's source text tells you what was declared. It doesn't tell you what won. A selector with higher specificity three files away, an inherited color from a grandparent, a !important buried in a vendor reset, a cascade layer ordering nobody remembers setting — any of these can silently override the rule a developer, or an agent, is staring at in the source. Before get_css_styles, an agent working through a CSS bug report had two bad options: ask the human to paste computed styles manually, or guess based on source order and hope the guess was right. Neither scales past trivial cases, and both erode the trust a team needs before letting an agent touch styling code unsupervised. Exposing the browser's own resolved answer — the actual matched and inherited rule set, not a static-analysis approximation of it — removes the guess entirely.
What this means for developers
- If you're already running an agent against your codebase, check your MCP server version.
get_css_styles only helps if the agent's tooling layer actually calls it; an outdated Chrome DevTools MCP install won't expose it even if the underlying Chrome build supports it. - CSS bug reports become a better fit for agentic triage. "This element has the wrong color on mobile" is exactly the class of ticket that stalled agents before — now the agent can request the computed value directly instead of asking a human to attach a screenshot of DevTools.
- This doesn't replace the Elements panel for exploratory debugging. It's built for programmatic, repeatable queries an agent issues as part of a workflow, not for a human visually scanning a layout — the two tools are complementary, not substitutes.
When does this ship / timeline
This is live now. Google's Chrome DevTools MCP team surfaced get_css_styles publicly around October 20, 2026, and it ships as part of the same Chrome 155/156 DevTools cycle the Chrome for Developers blog rounded up for November — no flag, no preview channel, no waitlist. Any team already using Chrome DevTools MCP to connect an AI coding assistant to a running browser gets the tool on update; the GitHub project tracks ongoing documentation and SKILL updates for how agents should call it. The more interesting open question isn't availability — it's adoption: how fast engineering teams rewire their agent workflows to actually use ground-truth computed styles instead of the source-reading habits those agents inherited from working with plain text.