Public Beta
Documentation
Getting started
Best practices
Help and support
Updates

Now works with any MUI version

April 2026

Highlights

  • Choose your Material UI and MUI X lines before Recipes generates the first implementation.
  • Stay on compatible pairings instead of mixing version lines that do not belong together.
  • Review the exact package versions included in the selected bundle before you start.
  • Copy dependency entries directly from the selector dialog when you need them outside Recipes.

Lock the package line before you prompt

The version selector now sits directly in the prompt toolbar on the Recipes home page.

Open it before you start a chat, pick the Material UI line you care about, and Recipes will keep the session grounded in that version context from the first response.

When you change the Material UI line, the MUI X choices are narrowed to the pairings that match it. That keeps the selection fast for most users and avoids combinations that would create friction later.

What the selector shows

The dialog is built to make the version choice explicit without taking over the prompt flow.

  • Material UI line cards let you choose the major line you want to target.
  • Filtered MUI X line cards show only the compatible MUI X options for that Material UI choice.
  • A compact label in the closed state keeps the selected pairing visible in the toolbar.
  • A package list shows the resolved bundle behind the selected pairing.
  • The copy dependencies action gives you ready-to-paste package entries when you need them.

Why this matters

Recipes is most useful when the generated code starts from the same package line your project actually uses.

With the selector in place, newer projects can stay on the latest stable pairing, while teams maintaining older lines can intentionally lock to those versions before asking for components, layouts, or bug fixes.

That reduces avoidable version mismatch problems and makes the generated starting point more predictable.

What's next

  • Keep improving version-aware flows across new chat, fork, and in-chat version handling.
  • Add more docs and examples around supported pairings and version-specific generation behavior.