ContactSign inSign up
Contact

Chromatic changelog: April 2026

PR comments, automatic flake tracing, and published MCP

loading
Varun Vachhar
— @winkerVSbecks
Last updated:

This month’s Chromatic release makes it easier to review and debug without leaving your usual workflow. Developers can now get test results directly in GitHub PR comments, and unstable snapshots now include Playwright traces automatically, so you can skip the manual rerun.

GitHub PR comments (beta)

Everyone reviewing a pull request can now see the UI test status without digging through the PR checks status list. Chromatic posts a comment that includes the number of visual and accessibility changes, plus a link to your published Storybook, so developers, designers, and anyone else in the review thread can see the latest status.

The comment updates automatically with each new build on the same PR.

Example of a PR comment that shows status and summary for UI Tests, UI Review and Storybook Publish

The comment is created the first time a build posts results for a PR, and updates automatically with each new build on the same PR.

This feature is opt-in per project. Enable it from your project’s “Manage” screen.

The Pull Request Comments option is available under the Notifications section on the project’s Manage screen.

Monorepo support

For monorepos linked to multiple Chromatic projects, you’ll see one comment per project. We’re actively working on consolidating results from multiple projects into a single comment.

Automatic tracing for unstable snapshots

Chromatic proactively identifies “Unstable” snapshots and includes a Playwright trace for them, no rebuild required.

With SteadySnap, Chromatic resolves a third of stability issues with snapshots. However, some issues require manual intervention. With automatic tracing, you can jump straight into the trace to diagnose what’s happening and fix it using the Chromatic snapshot troubleshooting guide.

Example build where Chromatic detected several unstable stories and attached traces for them

Publish your Storybook MCP server with Chromatic

Last month we launched the Storybook MCP server so AI agents can understand your component library and reuse existing components instead of inventing new ones.

Chromatic automatically publishes an MCP server for your Storybook, giving agents access to your approved components and patterns. This helps agents reuse what you’ve already shipped to build UI that matches your product.

Check out our quickstart guide to started →

Workflow diagram showing AI-assisted UI generation: a person submits a prompt, AI agents build components by referencing Storybook component metadata, and the resulting generated UI is reviewed by humans.

Did this article help you?

Get free UI development guides and tutorials like this emailed to you.

4,217 developers and counting

We’re hiring!

Join the team behind Storybook and Chromatic. Build tools that are used in production by 100s of thousands of developers. Remote-first.

View jobs

Popular posts

Published Storybook MCP servers

Give your entire organization access to a shared MCP instance to improve generated code quality. Chromatic manages publishing, auth, and versioning.
loading
Varun Vachhar

Storybook security advisory

Impacted versions 7–10. Patches available now.
loading
Dominic Nguyen

Chromatic changelog: Dec 2025

Accessibility testing updates for faster triage and Page Shift Detection upgrades
loading
Varun Vachhar
Company
AboutCareersTerms of ServicePrivacySecurity • SOC 2StatusContact Sales
Chromatic
© Chroma Software Inc. Made by the maintainers of Storybook.