vercel

ai-elements

AI Elements is a component library and custom registry built on top of shadcn/ui to help you build AI-native applications faster.

by vercel

TypeScript

TypeScript87.7%
MDX12%
CSS0.2%
JavaScript0.1%

Commit activity

Last 12 weeks · 4 commits

Full graph →

Community health

4 of 6 standards met

Community profile →
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Active · Last activity 6d ago
See all on GitHub →
NicolasMilliard

Summary Fixes #518. When uses , the textarea remains editable while an async submission is pending. A successful submission previously cleared the current draft, including text entered after submission started. The provider now clears its text only if it still matches the submitted text. Tests cover edits made during a pending submission, an unchanged draft after success, and a failed submission. Validation — 961 tests passed — passed Direct Oxlint and Oxfmt checks on both changed files — passed

NicolasMilliard · 1d ago
BHznJNs

Currently the ToolOutput component implementation has a guard statement: The expression will wrongly returns true when the output is an empty string. And for example, I have a read_file tool, and the agent use it to read a empty text file, sometimes the tool implementation will return an empty string here, and this expression will make the tool result be hidden.

BHznJNs · 1w ago
nsxdavid

Problem With , an async keeps the text until the promise resolves, which is good for retrying a failed send. But after it resolves, calls , which clears the current draft, not the text that was submitted. The textarea stays editable while the promise is pending. Anything typed during that time is erased when the send succeeds. Reproduction 1. Wrap in . 2. Use an that resolves after a delay, e.g. . 3. Type "first" and press Enter. 4. While the promise is pending, type " second" (or replace the text). 5. When the promise resolves, the textarea is emptied and the newer text is lost. Expected Only clear the draft if it still equals the submitted text, e.g. a functional update in the provider: (Alternatively, disable the textarea while a submission is pending.) Environment from the current registry (), React 19.

nsxdavid · 1w ago
shadcn

The Release workflow has failed on every push to since 2026-05-27, so nothing has published to npm since then. That includes the CLI deprecation notice from vercel/ai-elements#519. The first step, , gets (404) because the GitHub App behind no longer exists. Its old "Version Packages" PRs, like vercel/ai-elements#394, now show a blank author. This PR drops the app token and uses the built-in : Removes the app token step and the custom git user. sets up itself. Sets so the Version Packages commit and release tags are created through the API and signed by GitHub. Without it, the org's required-signatures ruleset would reject the push. Before merging A repo admin needs to turn on Settings → Actions → General → Allow GitHub Actions to create and approve pull requests. Otherwise changesets can't open the Version Packages PR. The Version Packages PR won't trigger , because PRs opened with don't trigger other workflows. The release job already runs before versioning. Follow-ups is broken by the same deleted app, but this switch can't fix it. It pushes straight to , which the org rulesets block for anything that can't bypass them. It needs either a bypass-capable app or a rewrite to open a PR. Once this works, delete the dead and secrets.

shadcn · 6d ago
shadcn

We are deprecating AI Elements at the end of November 2026 and replacing it with AI Elements from shadcn/ui. This PR adds: README. A warning callout under the title in the root README and the CLI README (the npm page). Docs site. A banner above the navbar on every page. Install docs. A "Starting a new project? Use shadcn/ui." callout above the installer on the Introduction page and under "Installing Components" on Setup. CLI. prints the notice to stderr before running . A patch changeset ships it in the next release.

shadcn · 6d ago
Structured data for AI agents

Repository: vercel/ai-elements. Description: AI Elements is a component library and custom registry built on top of shadcn/ui to help you build AI-native applications faster. Stars: 2496, Forks: 290. Primary language: TypeScript. Languages: TypeScript (87.7%), MDX (12%), CSS (0.2%), JavaScript (0.1%). Homepage: https://elements.ai-sdk.dev Topics: ai, elements, shadcn-ui, vercel. Latest release: ai-elements@1.9.1 (6d ago). Open PRs: 74, open issues: 49. Last activity: 6d ago. Community health: 87%. Top contributors: haydenbleasel, dependabot[bot], tobiasbueschel, unclebay143, FranciscoMoretti, chaxus, Debbl, obadakhalili, smorimoto, vercel[bot] and others.