GAIA UI Component Registry
Production-ready React UI components for building AI assistants and chatbots, installed directly into your codebase so you don't have to build conversational UIs from scratch.
Per-dimension scores and reasoning
Evidence shows a shadcn-style UI component registry, not an Agent with runtime privileges; no malicious indicators, but no documented posture on privileges, confirmation, data flow, or sensitive data, so those score 1. Dependencies are fully declared but include the suspicious [email protected] stub package and no audit evidence, so dependency_security is 1. Installer fetches code from external URLs with no rollback guidance. Source attribution is clear (company, repo, MIT), scoring 2.
README, package., and CI workflows are mutually consistent (v0.3.4, changeset flow), scoring 2. Dependencies are mainstream, but the fs stub and the unused @heroui/react dependency (contradicting the claimed HeroUI migration) are deducted. No error-handling or failure-message evidence at all, scoring 1.
Target audience and scenario (conversational AI UI builders) are well described, scoring 2. Beta status and API-change boundaries are declared, scoring 2. No agent trigger surface exists, so trigger_precision is 1. Good fit with Next.js 15/Tailwind v4/shadcn documented, scoring 2.
Clear layered docs (README/REGISTRY/ROADMAP), scoring 2. Installation notes are thorough (npx, shadcn CLI, components.), scoring 3. Naming is stable under @heygaia/ui but beta APIs may change, scoring 2. Examples point mostly to the external docs site, scoring 2. Beta limitations declared, scoring 2. Full MIT text present, scoring 3. Changesets with CI enforcement but no CHANGELOG file visible, scoring 2. Maintainer and support channels exist, scoring 2.
Components ship as paste-in source (shadcn model), reasonably usable, scoring 2. Claimed production-proven differentiation is not demonstrated inside the repo versus generic shadcn components, scoring 2. Low install cost for moderate benefit, scoring 2.
Promotional claims ('battle-tested', 'production-ready') are not traceable in the repo, scoring 1. Cross-corroboration is limited to the project's own site and social channels with an unverified publisher, scoring 1. Facts (version, license, dependencies) are clearly separated from inference, scoring 2.
- This repository is a UI component registry, not an executable Agent; most trust criteria lack applicable evidence and should not be read as an Agent security model.
- The [email protected] stub package in dependencies is suspicious/meaningless and should be removed; audit the full dependency tree.
- Install commands fetch and execute registry code from ui.heygaia.io; supply-chain trust rests entirely on an unverified publisher.
- Claims such as 'battle-tested in production' cannot be verified from the repository.
- @heroui/react remains in package., inconsistent with the README's claimed HeroUI migration; confirm whether it is redundant.
What does this agent do, and when should you use it?
GAIA UI (theexperiencecompany/gaia-ui) is an open-source UI component registry by The Experience Company, publishing the conversational interface components GAIA itself uses in production. It follows the shadcn registry distribution model: components are pulled into your project as source code via npx @heygaia/ui add or the shadcn CLI, rather than consumed as an npm dependency. The stack is React, TypeScript, Next.js 15, Tailwind CSS v4, Radix UI, and Framer Motion, with documentation hosted at ui.heygaia.io. The project is in beta — the team is migrating components out of GAIA's internal codebase, replacing HeroUI with shadcn/ui — and APIs may change before v1.0. It is a strong fit for frontend teams building chat or assistant interfaces who accept that the component set is still evolving and depends on the shadcn/ui ecosystem.
The repository is not an Agent itself; it is a component registry for AI assistant and chat interfaces. It provides production-tested components such as navbar-menu, raised-button, chat-bubble, and tool-calls-section, which developers install into their own projects via npx @heygaia/ui add <component> or npx shadcn@latest add https://ui.heygaia.io/r/<component>.. Standard shadcn/ui base components (button, tooltip, avatar, dropdown-menu, popover, skeleton) must be installed separately first. Components are maintained as source under registry/new-york/ui/, registered in registry., and built with pnpm run registry:build. The documentation site offers live examples and an API reference (ui.heygaia.io); contribution guidelines and the roadmap live in REGISTRY.md and ROADMAP.md.
- A team building a chatbot or AI assistant frontend in React that wants chat-bubble and tool-calls-section style conversational components instead of building them from scratch
- A frontend developer with an existing shadcn/ui project who can configure the @heygaia namespace in components. and incrementally install only the components they need
- A product team that cares about accessibility, responsiveness, and performance and prefers components battle-tested in GAIA's production over generic alternatives
- An open-source contributor wanting to add conversational UI components by forking the repo, creating components under registry/new-york/ui/, and submitting a PR per REGISTRY.md
- A team migrating from HeroUI to shadcn/ui looking for a working reference on migration and bundle-size optimization
What are this agent's strengths and limitations?
- Components are battle-tested in GAIA's production environment and designed for conversational UI edge cases, not generic repackaged widgets
- shadcn registry model means component source code lands in your project — fully customizable with no upstream npm dependency to manage
- Built on Radix UI primitives and Tailwind CSS v4, with documented focus on accessibility, responsiveness, and performance
- Active community: Discord server, public roadmap (ROADMAP.md), and a thorough contributing guide (REGISTRY.md)
- MIT license, free to use in commercial projects
How do you install or deploy this agent?
Prerequisites: Node.js, the shadcn CLI, and a package manager (the repo uses pnpm for development). Steps:
- Install shadcn/ui base components: npx shadcn@latest add button tooltip avatar dropdown-menu popover skeleton
- Add components via the GAIA CLI: npx @heygaia/ui add navbar-menu
- Or add multiple at once: npx @heygaia/ui add raised-button chat-bubble tool-calls-section
- Or use the shadcn CLI with the registry URL: npx shadcn@latest add https://ui.heygaia.io/r/navbar-menu.
- Or configure {"registries":{"@heygaia":"https://ui.heygaia.io/r/{name}."}} in components., then run npx shadcn@latest add @heygaia/navbar-menu
For contributing: fork the repo, run pnpm install, start the dev server with pnpm run dev, build the registry with pnpm run registry:build, and type check with pnpm run type.
How do you use this agent?
- Add components to your React/shadcn project using the commands above — the component source lands in your codebase and is yours to modify. 2. Browse live examples and the API reference at https://ui.heygaia.io. 3. When developing components locally, test them with npx shadcn@latest add http://localhost:3000/r/[component-name]. from the local dev server. 4. Get help via the Discord community (discord.heygaia.io) or report issues on GitHub. Note: the project is in beta and APIs may change before v1.0, so watch for breaking changes when updating components.