shadcn, the design engineer behind the widely adopted shadcn/ui project at Vercel, has introduced a new set of components for building chat interfaces, marking the first time streaming conversation primitives have been integrated directly into shadcn/ui. The release includes five components—MessageScroller, Message, Bubble, Attachment, and Marker—alongside two CSS utilities called scroll-fade and shimmer. It's described as the opening phase of a broader initiative to reimagine the abstraction layer for conversational interfaces, shipping components incrementally so developers can copy, adapt, and assemble them as needed.
At the core sits MessageScroller, the scroll container that handles technical details like anchored turns, streamed replies, saved thread restoration, prepended history, jump-to-message functionality, scroll controls, and visibility tracking. The component manages these behaviors without controlling messages, AI state, transport, persistence, or model state, meaning developers supply their own content renderer. Surrounding MessageScroller, the Message component arranges a conversation row, Bubble renders the message surface with reactions and buttons, Attachment manages files and images with upload state, and Marker displays status updates and separators for tool activity and date breaks. shadcn also launched @shadcn/react, a new package for unstyled, headless components starting with message-scroller, which lets the team ship tested interaction logic without tying it to a specific visual style. Everything works with both Radix and Base UI.
According to the report, Vercel CEO Guillermo Rauch declared that "The UI for AI is here. It's @shadcn," and the announcement attracted more than 950,000 views within days. shadcn clarified that the release doesn't replace Vercel's AI Elements, which is built on shadcn/ui with over 20 components tied to the AI SDK useChat hook—existing users don't need to rewrite anything and should only reach for the shadcn/ui version when they want the newer abstraction, updated styling, or Radix and Base UI support. A GitHub issue reported that MessageScroller mount-time anchors aren't applied, reproducible with the headless primitives alone, while broader sentiment on Hacker News continues to favor the copy-paste model, with developers noting they can upgrade components individually and avoid version lock-in common to libraries like MUI.
The release reflects shadcn's belief that chat has become a default interface worth standardizing, one primitive at a time, by folding patterns already present in community alternatives like Blazity's shadcn-chatbot-kit and ibelick's prompt-kit directly into shadcn/ui itself. The move comes as shadcn/ui has become one of the most widely adopted approaches to building React interfaces, with more than 121,000 GitHub stars and a registry now serving over 10 million components weekly. Rather than shipping as an installable dependency, it provides developers with copy-and-paste components built with React and Tailwind CSS that they own and customize, working across both Radix and Base UI primitives. For anyone moving from the styled components to the headless package, the documentation provides a direct parts mapping, where MessageScroller becomes MessageScroller.Root and MessageScrollerProvider becomes MessageScroller.Provider. The project is open source and MIT licensed, created by shadcn, a design engineer on Vercel's AI team. By standardizing conversational UI patterns at the component level, shadcn is placing a bet that the primitives of chat interaction are now mature enough to warrant the same treatment as buttons, dropdowns, and modals—commoditizing what was recently custom work into a reusable foundation. That shift could reshape how teams allocate engineering time, freeing developers from repetitive interface plumbing to focus on the logic and data that differentiate their products.