agent-ui vs stockbot-on-groq
Two of the top agent ui and generative ui, side by side: score, setup, license, activity and what each review found.
agent-ui
Next.js chat frontend for Agno AgentOS with tool calls and reasoning
stockbot-on-groq
Groq chatbot answering with TradingView widgets via AI SDK generative UI
| What we compare | agent-ui | stockbot-on-groq |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 51, popular | 40, known |
| Freshness | 76, recent | 20, quiet |
| Maintenance | 0, weak | 0, weak |
| Easy to run | 33, some setup | 33, some setup |
| Agent-ready | 0, none | 0, none |
| Facts from GitHub and the README | ||
| Stars | 1.9k | 1.5k |
| License | MIT (permissive) | Apache-2.0 (permissive) |
| Last commit | May 2026 | Dec 2025 |
| Last release | None published | Aug 2024 |
| Language | TypeScript | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
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
stockbot-on-groq
A Next.js chatbot forked from the Vercel AI Chatbot template where Llama 3 70B on Groq picks a tool and the UI renders a TradingView widget: price charts, financials, news, market overview, screeners, heatmaps and trending lists. Two sequential model calls produce the tool choice and the reply, one secret (GROQ_API_KEY) runs it, and there is no auth or persistence. For developers who want a worked example of tool-driven generative UI.
Who it is for: Developers wanting a worked example of tool-driven generative UI
Strengths
- Nine widget types show the tool-to-component mapping end to end
- Hosted demo at groq-stockbot.vercel.app
- Single env var to run
Weaknesses
- Groq-only; model pinned to Llama 3 70B in prompts
- Widgets are TradingView embeds, not your own data
- No auth, history or tests
- Last commit 2025-12
- TypeScript, groq, ai-sdk
- Needs groq-api-key
- env example file