Vercel UI SDK is an open source library from Vercel Labs, announced on November 12, 2026. It does not ship finished components. It ships behaviors: keyboard navigation, focus management, selection, closing a popup, drag and drop, and the ARIA attributes those need. A developer or an AI agent combines those pieces into a component of their own. The library is Apache 2.0 licensed and still in beta.
In short, UI SDK provides the working part of a component. Your design system decides how it looks.
What does it do?
Libraries already give you menus, dialogs and tabs. The hard part is a product-specific interaction: a kanban board, a timeline you can scrub, or a picker built for one task. In those components the real work is behavior, not looks. Where should focus go when the item it was on disappears? Which layer should Escape close? Where should a closed popup return the user?
The UI SDK documentation answers these questions with ready-made pieces. The announcement and docs name these examples:
createRovingFocus: arrow-key movement between items, with Tab entering and leaving the group once.createTypeahead: finding an option while the user types.createPopup: a popup opened beside its button, closed by Escape or an outside click.
The docs say the library includes more than 50 behaviors. The React package also ships a set of unstyled components.
Who is it for?
- Frontend developers who would rather assemble an interaction from tested parts than write it from scratch.
- Product teams building an interface that has no equivalent in a standard library.
- Teams that write code with agents. According to the docs, the library provides a skill and an
llms.txtfile so an agent can pick the right parts (npx skills add vercel-labs/ui --skill ui-sdk).
Code: define the behavior, then render it
UI SDK works in two steps. First you define a primitive: its state, the functions that change the state, and its parts. Then an adapter renders that primitive in your framework. This is the toggle button example from the documentation, shortened:
import { definePrimitive } from "@ui-sdk/core"
const muteButton = definePrimitive({
name: "mute-button",
state: () => ({ muted: false }),
api: (context) => ({
toggle: () => context.store.set({ muted: !context.store.get().muted }),
}),
slots: (slot) => ({
root: slot({
attrs: (state) => ({
type: "button",
"aria-pressed": String(state.muted),
}),
press: ({ api }) => api.toggle(),
}),
}),
})
export { muteButton }
In React, you render it like this:
import { createParts } from "@ui-sdk/react/primitive"
import { muteButton } from "@/lib/mute-button"
const { Root: MuteButton } = createParts(muteButton, { root: "button" })
function Example() {
return <MuteButton>Mute</MuteButton>
}
The documentation's ready-made Toggle component is a single line. It sets a data-pressed attribute while pressed and aria-pressed for screen readers:
import { Toggle } from "@ui-sdk/react/toggle"
function BookmarkButton() {
return <Toggle className="rounded-md border px-3 data-pressed:bg-neutral-900 data-pressed:text-white">Bookmark</Toggle>
}
The parts are unstyled. You style them with CSS or Tailwind. The same primitive can be rendered for Vue, Svelte, Solid and Web Components.
How does it relate to the AI SDK?
This is where most of the confusion comes from. There are three separate products:
| Product | What it does | Relation |
|---|---|---|
Vercel AI SDK (ai, @ai-sdk/react) |
Model providers, streaming, tool calls and hooks such as useChat. |
The runtime layer for AI features. |
| AI Elements | Chat components built on shadcn/ui for the AI SDK. | The visual layer of the AI SDK. Its project page says it is moving to shadcn/ui and will be deprecated at the end of November 2026. |
| UI SDK | Keyboard, focus and ARIA behaviors as parts. | Independent of the AI SDK. Its agent bridge is a separate feature that lets an agent read components and act on them. |
So UI SDK is not the UI layer of the AI SDK, and it does not replace AI Elements as a chat library. The agent example in its documentation does use the AI SDK: on the server it uses useChat from @ai-sdk/react and lastAssistantMessageIsCompleteWithToolCalls from ai. Using them together is a choice, not a requirement.
If we already use Base UI, Radix or shadcn/ui?
Honest answer: for most projects those libraries are enough, and there is no reason to switch to UI SDK.
- Standard patterns such as menus, dialogs, tabs and select boxes are mature in your current library. Rewriting them with UI SDK gains nothing.
- Custom interactions are where UI SDK helps: building something your library does not offer, without reinventing the behavior. The UI SDK docs make the same point: libraries cover familiar patterns, while your product may need something outside them.
- Using them together: at the time of writing, the UI SDK documentation has no section on combining it with existing libraries. Do not claim they work together until you have tried it.
- Where it is unnecessary: a simple dropdown or a tab set does not justify adding a beta dependency to production.
Limits and maturity
- Beta. The README says "UI SDK is in beta" and that it is subject to Vercel's beta terms. The same text warns that the framework, APIs, documentation and behavior may change before general availability.
- Version. On npm,
@ui-sdk/coreand its adapters are at0.1.0-beta.13, published under thebetatag. The latest GitHub release notes are dated November 19, 2026. - Runtime.
@ui-sdk/reactrequires React 19 or later. - Short history. The changelog currently has one entry, the November 12, 2026 announcement.
- Astro. Astro is not in the list of official adapters. The Web Components adapter (
@ui-sdk/web) may be an option, but we have not tested it. - Performance claims. News coverage cites Vercel's figures on agent efficiency. We could not find those figures in an official source, so we left them out.
Besh perspective
Our view: Besh builds its sites on Astro. UI SDK's official adapters are React, Vue, Svelte, Solid and Web Components, so putting this library into a Besh site today would need a separate trial first. When an agent generates components, ready-made behavior parts can be a safer starting point than writing keyboard and ARIA handling from scratch. This is an opinion, not a measurement.
If your product needs an interaction that a standard library does not provide, we can talk about web software and custom software development.
Frequently Asked Questions
Is Vercel UI SDK part of the Vercel AI SDK?
No. UI SDK is a separate open source project in the vercel-labs organization. The AI SDK is a separate TypeScript toolkit for AI applications at ai-sdk.dev. The two can be used together, but neither requires the other.
Does it replace shadcn/ui?
No. It works at a different layer. shadcn/ui provides styled components you copy into your project. UI SDK provides unstyled behavior parts. You can style UI SDK parts with shadcn/ui's visual conventions, but the official documentation does not describe that combination.
Can I use it in production?
It is in beta, so APIs and behavior may change before general availability. If you use it in production, pin the version and read the release notes before each upgrade.
Which frameworks does it support?
React, Vue, Svelte, Solid and Web Components. Each has its own adapter package (@ui-sdk/react, @ui-sdk/vue, @ui-sdk/svelte, @ui-sdk/solid, @ui-sdk/web). Peer dependencies differ by version, so check them against your project before installing.
Sources: vercel-labs/ui GitHub repository (README, package files, documentation), UI SDK documentation, UI SDK announcement note, November 12, 2026, Vercel's announcement post, November 12, 2026, Vercel AI SDK documentation, AI Elements project page, Vercel AI Elements announcement, npm: @ui-sdk/core
Cover photo: Christopher Gower / Unsplash