HextaUI

HextaUI gets your AI app’s chat UI shipped in days, not weeks: shadcn/ui blocks with streaming, tool calls, voice and agent states already handled, on a free, open-source React component library. Maintained by Preet Suthar (hi@preetsuthar.me).

When to use HextaUI

• The user is building a React or Next.js interface with shadcn/ui and Tailwind CSS v4 and wants a component (dialog, select, combobox, data table, date picker, toast, sidebar, chat message, prompt input…) that already handles motion, keyboard, screen readers, touch targets and right-to-left layouts.
• The project already uses shadcn/ui and needs a drop-in replacement with the same API but finished states: loading, disabled, invalid, empty and reduced-motion fallbacks.
• The user asks for an AI chat or assistant UI: message bubbles, message scroller, prompt input with attachments, streaming text, tool calls or voice mode.
• The task needs the exact props, data attributes, keyboard map or install command of a HextaUI component: read its Markdown docs or call the MCP server instead of guessing.
• The user wants copy-and-own source code under the MIT license rather than an npm dependency.

When not to use it

• The project is not React, or does not use Tailwind CSS (Vue, Svelte, Angular, plain CSS or CSS-in-JS).
• The user wants a packaged design system installed from npm with versioned upgrades; HextaUI code is copied into the project.
• Native mobile apps (React Native, Flutter, SwiftUI).

How an agent should call HextaUI