Our upcoming public API lets agents test their own frontend work, diagnose what failed, and fix it in the same loop. Join Jarel Fryer and Varun Vachhar for a live preview and our roadmap for agents. Register in comments 👇
Chromatic
@chromatic.com
Our mission: to improve the UX of the Internet. Core maintainers of Storybook and makers of Chromatic.
Flaky tests shouldn't block your build. Meet Flake filter: Chromatic now auto-detects unstable tests, so you can focus on real changes without getting blocked by flakes. 🧵
The frontend bottleneck is no longer code generation. It's now reviewing the output of an agent. Storybook is working on two things to fix that: ✅ Claude Code + Codex plugins ✅ Agentic review to surface key changes Join Storybook team for a live walkthrough + Q&A. Register in comments 👇
Visual bugs don't always show up in your test suite. Kyle Gach from Chromatic shares how visual testing complements Vitest Browser Mode, helping catch the layout, styling, and responsive regressions that traditional component tests can miss. Early access is now open: tympanus.net/codrops/?p=1...
Get first access to our @vitest.dev plugin, which adds Chromatic’s visual testing and review to your browser tests. It’s built by @ariperkkio.dev, a Vitest core maintainer. It’s free to use while in beta and requires no changes to your test files. Read on for more info 🧵
AI gets you to prototype fast. The hard part is proving the next prompt didn’t break the UI. Join @bolt.new CEO, Eric Simons and Chromatic CEO, Zoltan Olah for a live session on taking AI-generated UIs to production with visual tests + human review. Register in comments👇
We’re launching early access for Vitest visual testing with Chromatic! ⚡️ Built with @vitest.dev core maintainer ariperkkio.dev, Chromatic adds visual testing to the browser tests you already write. 🧵 (1/4)
📱Announcing beta Chromatic support for visually testing React Native apps! If you already use Chromatic, this workflow should feel familiar: Push a change → Chromatic captures rendered native UI → visual regressions show directly in your PR. 🔍✨ (1/3)
Is your component library lighting up in errors and not sure how to tackle it? 👀 On Thursday, we’re showing how teams use parallel AI agents with Storybook + Chromatic to triage, fix, validate, and retest accessibility issues simultaneously. Register in comments 👇
Many a11y issues are repetitive, straightforward, and ideal for parallelized AI workflows. 🤖 Learn how to use Storybook + Chromatic to: ✅ Detect issues ✅ Parallelize remediation ✅ Use AI agents to fix + retest ✅ Validate fixes in Storybook 🎟️ Register in comments 👇
Our April changelog is out: 🔀 PR comments: Your test results and Storybook link right in the PR comment 🫨 Auto Playwright traces on unstable snapshots (no rerun needed) 🤖 Publish your Storybook MCP so agents reuse your approved components Read the full changelog 👇
AI agents are changing frontend dev and Storybook is evolving to keep up. Join our session where we share what’s next: ✨ review only changed stories ⚡ faster setup with agents 🧩 10x faster, more complete docgen 🛠 skills with Storybook Register for the live Q&A + to receive the recording👇
Want to hear directly from the team behind Storybook MCP? Join our live AMA where we’ll cover why we built an MCP server, how agents helped us move faster with more rigor, our eval tooling, and what’s next. 🗓️ Tuesday, March 31, 2026 ⏰ 2:00 pm EDT / 20:00 CET Register in comments👇
Announcing Storybook MCP for React + publishing on Chromatic 🎉 🧵 ⤵️
Storybook MCP for React is here 🎉 Storybook MCP gives AI agents structured context from your components and design system to build better UI the first time. 🧵 ⤵
AI agents write better UI with the right context. Storybook MCP gives them access to your components, stories & tests so they can build, preview & validate UI from a single prompt. Join us for a walkthrough of the workflow + a sneak peek of upcoming features. Link in comments 👇
Frontend perf gets deferred until UX lags & you’re debugging in prod. Matthew Costabile (@github.com) is joining Dominic Nguyen (Chromatic) live on GitHub’s approach, their new Storybook perf addon & how component-first measurement complements prod monitoring. Register in comments👇
What if your UI didn’t have to be decided at build time? Generative UI lets AI assemble the components you already ship using intent, state + data to render UI needed in the moment. We’re walking through how this works live with @mrmagan.bsky.social (Tambo). Register in comments 👇
Generative UI isn’t AI writing code. It’s assembling your tested components based on intent, state & data. That only works if your component library is reliable. We’re digging into the React workflow live with @mrmagan.bsky.social (Tambo). Register to join live & get the recording 👇
Frontend dev is a feedback loop: build → test → review → ship. AI speeds it up, and can ship slop just as fast. Here’s a practical guide for humans + agents to share the same loop using functional + visual + a11y checks to keep UI stable while shipping faster. 👇 link in comments
🚀 New Chromatic updates are here. We’ve been sharpening the testing experience so teams can spot issues earlier and triage way faster. Accessibility testing, UI clarity, and Page Shift Detection all got meaningful upgrades. 🧵 (1/7)
AI is beginning to use design systems exactly as documented. Gaps in examples, states & constraints lead directly to unpredictable UI output. Join Brad Frost + Dominic Nguyen in a live session to cover what makes a system agent-ready. 📆 Dec 11 • 12PM ET 🔗 Registration link below
Agents can’t “just read the repo.” Thousands of files + type soup = instant confusion. Storybook MCP gives agents only the good stuff—curated patterns from your stories, docs & tests—and a loop to self-fix with your component tests. Link to request early access in comments 👇
UI testing covers a huge surface area—logic, visuals, interactions, a11y, user flows. The challenge isn’t running tests; it’s choosing the right approach. We break down a component-driven strategy that aligns with how modern UIs are built. 👉 www.chromatic.com/blog/how-to-...
🧵 (1/3) Most AI-generated code looks good until you try to merge it. Wrong props, odd states, subtle regressions. Storybook MCP fixes that. It turns your stories, docs & tests into machine-readable context so agents actually follow your patterns.
Most teams fix a11y issues. Not all stop creating new ones. Tomorrow, our product team is sharing how we built a system that does both—cutting 15k+ violations without slowing delivery. Join us live & bring your questions! 📅 Nov 13 • 12 PM ET / 18 CET 👉 Register in comments
We cut our a11y issues by 94% after we stopped treating them as tickets & started treating them as system flow. Then we blocked new regressions in CI, inflow dropped to zero & the backlog finally moved. Now we’re sharing how we did it in a live session. 🔗 Link in comments