agent-chat-ui vs agent-ui
Two of the top agent ui and generative ui, side by side: score, setup, license, activity and what each review found.
agent-chat-ui
Next.js chat frontend for any LangGraph server with interrupts and artifacts
agent-ui
Next.js chat frontend for Agno AgentOS with tool calls and reasoning
| What we compare | agent-chat-ui | agent-ui |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 74, popular | 51, popular |
| Freshness | 100, active | 76, recent |
| Maintenance | 31, patchy | 0, weak |
| Easy to run | 0, hard | 33, some setup |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 3.2k | 1.9k |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | May 2026 |
| Last release | None published | None published |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
agent-chat-ui
A Next.js frontend that connects to any LangGraph server exposing a messages key: enter the deployment URL and assistant ID (or set them as env vars) and you get streaming chat, tool-call rendering, human-in-the-loop interrupts and an artifacts side panel. A built-in API passthrough route injects your LangSmith key server-side for production. For teams that have a LangGraph backend and need a UI today.
Who it is for: Teams with a LangGraph backend that need a chat UI
Strengths
- Works against local and deployed LangGraph servers with no backend changes
- Hosted version at agentchat.vercel.app and an npx scaffold
- Message hiding and artifact rendering conventions are documented
- Tests included; committed within the last two days
Weaknesses
- The passthrough proxy does not authenticate callers; README warns it exposes your deployment
- Production auth requires custom LangGraph authentication and code edits
- LangGraph SDK only; no AG-UI or AI SDK stream support
- No persistence of its own; threads live in the LangGraph server
- TypeScript, langgraph
- Needs langgraph-server, langsmith-api-key-for-deployed-servers
- env example file
agent-ui
A Next.js and shadcn/ui chat interface that connects to a running Agno AgentOS instance (default localhost:7777) and renders streamed replies, tool calls with results, reasoning steps, references and image, video or audio content. Auth is a bearer token set via NEXT_PUBLIC_OS_SECURITY_KEY or the sidebar; the main branch targets Agno v2 and a v1 branch remains. For Agno users who need a frontend without writing one.
Who it is for: Agno users who need a chat frontend
Strengths
- Scaffolds with npx create-agent-ui; endpoint and token editable in the UI
- Renders reasoning steps, references and multimodal outputs, not only text
- Separate branch kept for Agno v1
Weaknesses
- Only speaks to AgentOS; no use outside the Agno stack
- Token is exposed as NEXT_PUBLIC and stored client-side
- No tests, no persistence of its own
- Last commit 2026-05
- TypeScript, agno
- Needs agno-agentos
- GitHub template