Changelog

A new Toast component is now available for Base UI projects. It supports actions, status types, promises, stacking, and swipe dismissal.

"use client"

import { Button } from "@/components/ui/button"

Add it to your project with the CLI:

pnpmnpmyarnbun
pnpm dlx shadcn@latest add toast
Copy

React Aria is now a first-class component base in shadcn/ui.

Build with React Aria Components alongside Base UI and Radix. Pick it in shadcn/create or initialize a project with --base aria. The CLI handles the dependencies, registry resolution, styles, and component installation.

What's New#

• A first-class React Aria base - Choose React Aria anywhere you can choose Base UI or Radix, including the CLI, presets, and shadcn/create.
• Full component documentation - React Aria components have dedicated installation, usage, composition, examples, and API reference sections.
• All eight styles - Use React Aria with Vega, Nova, Maia, Lyra, Mira, Luma, Rhea, or Sera.
• Base-specific output - React Aria state selectors and dependencies are scoped to the Aria registry. Existing Base UI and Radix components are unchanged.

Start with React Aria#

Use the aria base when initializing a project:

pnpmnpmyarnbun
pnpm dlx shadcn@latest init --base aria
Copy

Or choose React Aria in shadcn/create. Once the project is initialized, shadcn add installs the React Aria implementation for each component.

Base UI remains the default, and Radix remains fully supported. Existing projects stay on their current base.

We are open sourcing @shadcn/helpers, a new package for small, focused helpers that make developing apps easier.

Starting with a helper for AI SDK and TanStack AI. It lets you write a conversation in code, then run it through the real useChat lifecycle without a model, API route, network request, or API key.

Your UI receives native framework messages and streaming events, so reasoning, tool calls, loading states, and message components behave the same way they do in production.

Here is a conversation written with the AI SDK helper:

Copyimport { createChat } from "@shadcn/helpers/ai-sdk"
 
const chat = createChat()
  .user("What changed in this release?")
  .assistant("The release adds keyboard shortcuts and faster search.")
  .user("Can you check the full release notes?")
  .sleep(500)
  .assistant(({ writer }) => {
    writer.stepStart()
 
    // Reasoning.
    writer.reasoning("I should read the release notes first.")
 
    // Tool call.
    writer
      .tool("getReleaseNotes", {
        title: "Reading release notes",
        input: { version: "latest" },
      })
      .sleep(500)
      .output({
        highlights: ["Keyboard shortcuts", "Faster search"],
      })
 
    // Source.
    writer.sourceUrl({
      title: "Release notes",
      url: "https://example.com/releases",
    })
 
    // Response.
    writer.text("The release adds keyboard shortcuts and faster search.")
  })

Pass its messages and transport to useChat:

Copyimport { useChat } from "@ai-sdk/react"
 
const initialMessages = chat.get(0)
const transport = chat.transport()
 
export function Chat() {
  const { messages } = useChat({
    messages: initialMessages,
    transport,
  })
}

The package includes two adapters:

• @shadcn/helpers/ai-sdk plugs into AI SDK's useChat as a transport.
• @shadcn/helpers/tanstack-ai plugs into TanStack AI's useChat as a connection and streams real AG-UI events.

Use it to build components, create previews and demos, write documentation, or test streaming interfaces with deterministic output and no backend dependency.

Today we're releasing shadcn/typeset: a styling system for HTML and rendered markdown, in one CSS file.

Your app renders the same HTML elements everywhere: headings, paragraphs, lists, tables, and code. You style them for your blog, then your docs, and now chat. Typeset lets you style them once, then tune the rhythm for each context.

Copy<div className="typeset">{content}</div>

Add one class and everything inside gets styled. Typeset follows the size of its container, uses your theme, and gives you three controls: size, leading, and flow.

You can create as many typesets as you need. Use a tighter rhythm for chat and a roomier one for docs:

Copy.typeset-chat {
  --typeset-leading: 1.6;
  --typeset-flow: 1em;
}
 
.typeset-docs {
  --typeset-size: 15px;
  --typeset-leading: 1.75;
  --typeset-flow: 1.5em;
}

Copy<div className="typeset typeset-chat">{message}</div>
<article className="typeset typeset-docs">{page}</article>

It's also designed for streaming, so new blocks don't restyle earlier ones. The file lives in your project. There's no package or config layer to work around.

Open the typeset builder to create yours, or read the Typeset docs for the full guide.

Starting today, Base UI is the default component library in shadcn/ui.

First, a bit of history. When shadcn/ui launched in January 2023, it was built on Radix. At the time, nothing else came close. Unstyled headless components, great APIs, great accessibility, battle-tested in millions of apps.

Fast forward a few years and the same folks who built Radix are building something new: Base UI. They've done it once. Now they get to do it again, with everything they learned the first time.

Last year, Base UI tagged a beta and a lot of you asked if we are going to replace Radix with it. I said "the worst thing you can do for your production app is switch component libraries". I meant it, and it still holds. So instead of switching, we did the shadcn thing: we rebuilt every component for Base UI, kept the same abstraction, and let you choose. December brought npx shadcn create with both libraries. January brought full Base UI docs.

Then we watched what you did with it.

Why Now#

• Base UI is stable. It's at 1.6.0 with 6M+ weekly downloads.
• It keeps getting better. The team ships new and useful components regularly.
• We use it. Every new project we've started runs on Base UI.
• You use it. Projects created on shadcn/create now pick Base UI over Radix 2 to 1.

The community already made the call. We're making it official.

What's Changed#

• New projects default to Base UI. Run npx shadcn init and Base UI is the default pick.
• shadcn/create shows Base UI first.
• The docs default to Base UI. Component pages open on the Base UI tab. Radix docs are one click away.

What This Means for You#

Radix is not being deprecated. We still support it, and every update and new component will ship for both libraries (unless a component only exists in Base UI).

You do not need to migrate. Radix is a mature, tested library. We still run it in production today and we're not migrating. If your app works, keep shipping.

Prefer Radix for new projects? It's one flag away:

pnpmnpmyarnbun
pnpm dlx shadcn init -b radix
Copy

If you have scripts or CI running shadcn init non-interactively and expecting Radix, add -b radix to keep them on the same path.

Building a registry? Ship a registry:base config if you want to pin a specific library. Items without one now init as Base UI.

Starting something new? We recommend Base UI.

When You're Ready to Migrate#

You don't need to migrate. But if you want to, we built a skill for it:

pnpmnpmyarnbun
pnpm dlx skills add shadcn/ui
Copy

Then ask your coding agent:

Copymigrate accordion to base-ui

It's progressive by default: migrate one component and its usage at a time while your project stays green and shippable. Both libraries coexist while you work. Stop halfway, ship, come back next week and it picks up where you left off. Or ask for the whole project in one go.

Why a skill and not a codemod?#

Because you own the code. You've added variants, changed classes, threaded new props. A codemod handles the components you never touched and breaks on the ones you did.

So we shipped knowledge instead: every rename, every prop change, every behavior difference, hand-checked against both libraries. Your agent reads it, figures out what you changed, and carries those changes over.

Mechanical things get fixed everywhere (asChild is now render). Behavior changes get flagged, never silently patched. You decide.

What a migration produces#

Every run leaves three things:

• Working code. Typechecked and built before it reports success.
• A report per component in .migration/ at your project root: what changed, what was left alone, and a short checklist of things to verify by hand.
• Clean git history. One commit per component, on a branch. Rollback is deleting the branch.

Here's what a report looks like:

Copy# accordion
 
<!-- date, strategy used, and the one-line verdict -->
 
## Changed
 
<!-- every file touched, with what changed and why -->
 
## Left alone
 
<!-- files that look related but were intentionally not touched -->
 
## Behavior changes
 
<!-- differences that compile fine but act differently. flagged, not patched -->
 
## Verify by hand
 
<!-- a short checklist: open, click, tab through. takes a minute -->

No hidden state. Progress lives in your files and git history, so any agent, any session, any day picks up where the last one stopped.

It works with Claude Code, Cursor, or any agent that supports skills. We tested it on real projects: 60+ components, 36 of them on Radix. A full migration ran in about 25 minutes at roughly 10k tokens per component. Clean builds, customizations intact.