← Back to all sparks
S

shadcn/ui

DESIGN
Velocity6.3

Open-source React component library

shadcn/ui is turning a component registry into infrastructure for AI app UIs.

component-registrybase-uiai-sdkchat-uiagent-toolingdesign-system
Current state
shadcn/ui has stopped being just a Radix-based component registry. It now supports three primitive bases - Radix, Base UI (the default since July) and React Aria - and has been shipping registry infrastructure of its own: GitHub-repo registries in June, server-side search in July. The newest work sits outside components entirely, in @shadcn/helpers, a utility package aimed at AI SDK and TanStack AI.
Where it's heading
Two arcs run in parallel. One is decoupling from any single primitive vendor, which turns the registry into a distribution layer rather than a wrapper around Radix. The other is a push up the stack into AI application code - chat interface components in June, typeset for streaming text in July, and now mocks for paused tool calls and approvals. The components are becoming a means to a larger surface.
Prediction
Expect the helpers line to keep extending along agent-workflow states - the entries so far move from introduction, to chat surfaces, to human-in-the-loop - and more composite patterns like Questionnaire rather than new primitives.

Recent moves

  1. 7d ago

    Helpers add mocks for paused tool calls and approvals

    The helpers package picks up mocking for paused tool calls, approvals and continuations - the human-in-the-loop states an agent UI has to render. It is the second drop on the @shadcn/helpers line in a month, filling in the AI SDK surface rather than widening it.

    View source ↗
  2. 14d ago

    Questionnaire component for multi-step question flows

    A multi-step question flow with fixed, freeform, multiple and skippable answers - a composite pattern, not a primitive. It continues the shift from low-level building blocks toward whole interaction patterns that started with the chat components.

    View source ↗
  3. 19d ago

    Registries can now handle search server-side

    Server-side search moves work out of the client and into the registry itself, which matters most for large or private registries. Registry plumbing has been a steady drumbeat since GitHub registries landed in June.

    View source ↗
  4. 27d ago

    Toast component built on Base UI primitives

    A Toast built on Base UI rather than Radix - a concrete instance of the default-base switch rather than a new capability. New components now arrive on the Base UI stack by default.

    View source ↗
  5. 1mo ago

    React Aria joins Radix and Base UI as a component base

    React Aria becomes a third supported primitive base alongside Radix and Base UI. The pluggable-base architecture was already declared when Base UI became the default; this broadens the options inside it rather than changing the shape.

    View source ↗
  6. 1mo ago

    @shadcn/helpers ships, starting with AI SDK and TanStack AI

    ⚡ SPARK

    The project steps outside its component-registry lane: helpers are application code, not UI primitives, and the first two targets are AI SDK and TanStack AI. Everything shipped since - the chat components, the human-in-the-loop mocks - reads as follow-through on this.

    View source ↗