Measured entry
hextaui-team-ai-room
A client-side React room shell for shared AI conversations, with participant avatars, message attribution, typing state, streaming display, and a composer. It ships as a shadcn registry block and relies on sibling HextaUI primitives, a class-name utility, Lucide icons, Radix primitives, theme support, and the React Markdown, GFM, and Shiki rendering stack.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 1 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 1942.5 KB (2007.9 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 39s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/team/team-ai-room.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A credible starting shell for a collaborative AI room, with useful controlled props and clean responsive behavior. It needs a shadcn-style setup, carries a substantial rendering stack, and should not ship until the send button receives an accessible name.
Use it if
- You already use shadcn conventions and want a composed team chat surface rather than a chat backend.
- Your application can supply participants, messages, streaming state, and async send and typing callbacks.
- You need assistant responses to support Markdown, tables, and highlighted code through the bundled message renderer.
Skip it if
- You need a standalone package with transport, persistence, authentication, presence, or model integration included.
- You are minimizing client bundle weight and do not need the Markdown and syntax-highlighting dependency chain.
- You cannot remediate the icon-only send button, which currently lacks an accessible name.
- Your project does not use shadcn-style aliases, utility classes, registry primitives, or theme conventions.
Install
| Declared dependencies | react-markdown, remark-gfm, shiki, next-themes, @radix-ui/react-slot, @radix-ui/react-dropdown-menu, @radix-ui/react-avatar |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add the source alias and class-name helper, configure Tailwind-compatible utility styles and theme variables, bring over the avatar, badge, card, empty-state, input-group, and AI-message components, and install Lucide, the required Radix primitives, theme support, React Markdown, GFM, and Shiki. Add an accessible label to the send control.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/preetsuthar17/HextaUIAlternatives
Other published entries for the chat pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hextaui-alertminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 26.8KB
- Bare
- fail
- Prov
- NO
- kibo-bannerminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 33.0KB
- Bare
- fail
- Prov
- NO
- ruixen-comment-threadunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 40.2KB
- Bare
- fail
- Prov
- NO
- ruixen-smart-paste-inputunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 44.4KB
- Bare
- fail
- Prov
- NO
- ruixen-faq-chat-accordionunclassified
- Renders
- YES
- A11y
- 0
- Gzip
- 67.7KB
- Bare
- fail
- Prov
- NO
- ruixen-gradient-chat-inputgradient-glow
- Renders
- YES
- A11y
- 0
- Gzip
- 72.6KB
- Bare
- fail
- Prov
- NO