▲ Introducing AI Elements by Vercel
@haydenbleasel18K followers
180,686 views
50 Comments
Comments from the original post on X (Twitter)

@haydenbleasel
Shoutout to the GOAT @ryanharaki_ for the collab on this. Also if you're familiar with the Kibo AI components, I donated them to Vercel to form the foundation of project! We've made some fantastic improvements though... 👇
23 likes

@haydenbleasel
1/ New Components As AI interfaces evolve, we're seeing more patterns emerge from concepts like RAG, MCP and Deep Research. To help build for these, we've created these additional components... 🖱️ Actions 🌉 Image 💬 InlineCitation 🌀 Loader ✅ Task 🖥️ WebPreview
13 likes

@haydenbleasel
2/ CodeBlock simplified for typical AI responses Code blocks in Markdown are typically simple. The Kibo UI code block, while very powerful, is too much overhead for this. We've rebuilt the Code Block component so it's a lot simpler.
9 likes

@haydenbleasel
3/ @v0 style icons Components like Reasoning, Source and Task now have icons prefixing their Trigger title, like you'd find on v0. This makes them much nicer to look at when used in a more agentic fashion.
9 likes

@haydenbleasel
4/ Animations All collapsible components (Task, Sources, Reasoning, etc.) have animations when you open and close them! A nice little quality of life improvement.
10 likes

@haydenbleasel
5/ A better Response component The Response component's react-markdown implementation is now wrapped in our markdown-sanitizers package (thank u @cramforce) to help secure your AI agents. It also has intelligent parsing that auto-completes unterminated formatting and hides incomplete links. Additionally, it can render mathematical equations now!
12 likes

@haydenbleasel
6/ Seamless integration with AI SDK Component types have been improved for more seamless integration with AI SDK. You can still bring any provider you'd like though 😅
8 likes

@haydenbleasel
7/ Misc rendering improvements There's been a ton of small tweaks around the place. For example, Tool component parameters are rendered in a CodeBlock!
13 likes

@haydenbleasel
We hope you enjoy AI Elements! Follow me @haydenbleasel for updates. Also, Like/Repost the quote below if you can:
15 likes

@ivasilov
@vercel @shadcn Shouldn't this Props subheading be named Components?
3 likes

@haydenbleasel
@vercel @shadcn
1 like

@ivasilov
@vercel @shadcn You've done an awesome job btw! I think we'll be migrating to these elements tomorrow :)
3 likes

@nbaschez
@vercel @shadcn this is awesome
3 likes

@sonofalli
@vercel @shadcn DOPE
3 likes

@rohandave_
@vercel @shadcn insane! do you plan to use this in Chat SDK repo instead of the custom UI components?
2 likes

@v0intern
@vercel @shadcn ok kinda based
2 likes

@gilgNYC
@vercel @shadcn Welcome! Would love to see artifacts.
2 likes

@nicoalbanese10
@vercel @shadcn Banger
2 likes

@elliothesp
@vercel @shadcn Very cool! I'm curious, the JSON on looks to be a single item schema, and it's installed with ?components=name... is this a new thing on Shadcn side?
2 likes

@haydenbleasel
@vercel @shadcn That's a dynamically generated registry pattern that I'll be sharing more about real soon 😄
1 like
























