Documentation
Recipes is now in public beta
May 2026
Highlights
- Alpha → beta. Recipes graduates from public alpha to public beta.
- Multi-version MUI support. Generate against the Material UI and MUI X line your project actually uses.
- Latest models. Routing now leans on the newest frontier models for higher-quality first drafts.
- Multi-step workflows. Recipes can plan, generate, and revise across multiple steps in a single turn.
- Smart autofixes. Generated code is cleaned up automatically before it lands in the editor.
- Refreshed design. A cleaner, more confident look across the chat home and chat view.
- Benchmarked. We measure quality against an internal benchmark suite on every change.
From alpha to beta
Public alpha proved the core idea: ask for a Material UI screen, get a working starting point. Beta is about making that starting point dependable enough to use day to day.
The behind-the-scenes pipeline has been rebuilt with a stronger workflow, better defaults, and a real evaluation loop. You should notice fewer broken first drafts, fewer follow-up clarifications, and a faster path from prompt to a screen you can actually run.
What's better in beta
Works with multiple MUI versions
Recipes now generates against the Material UI and MUI X line that matches your project, with compatible pairings enforced. Older projects can stay on the line they need; newer projects get the latest stable defaults.
Latest models, picked for the job
Behind the scenes, prompts route to the most capable models available, with the right model picked for the right step instead of one model doing everything.
Multi-step workflows
Single-shot generation works for small asks. Real screens often need planning, drafting, and revising. Recipes now does that work inside a single response, so you get a more complete result without manually re-prompting.
Smart autofixes
The output is run through a layer of automated fixes — API migrations, common mistakes, and version-aware adjustments — before it reaches your editor. Less time spent fixing the model, more time spent on what you actually wanted to build.
A nicer place to work
The chat home, message rendering, and source view have all been polished. Tools, code blocks, and version status are easier to read, and the home page feels less busy.
Benchmarked, not vibes
Every meaningful change is now scored against an internal benchmark so we can tell whether quality is actually going up. Fewer regressions, more confident improvements.
More to come
Beta is a milestone, not the finish line. Expect continued investment in workflow quality, model selection, version-aware generation, and the surrounding tools.
Thanks for using Recipes through alpha — beta is built on what you helped us learn.