Agent UI and generative UI

Frontends that render agent steps, tool calls, approvals or model-generated components.

agent-chat-ui leads with 45, ahead of OpenGenerativeUI (45) and agent-ui (40). 6 projects ranked by score.

The ranking

Agent UI and generative UI: full ranking
RankProjectAdoptionFreshnessMaintenanceEasy to runAgent-readyScore
1agent-chat-uiNext.js chat frontend for any LangGraph server with interrupts and artifacts Live demo ↗ (opens in a new tab)3.2k stars, MIT, last commit Oct 202674100310045 out of 100
2OpenGenerativeUIChat interface that answers with 3D models, charts, calculators and maps2.4k stars, MIT, last commit Oct 2026631003004045 out of 100
3agent-uiNext.js chat frontend for Agno AgentOS with tool calls and reasoning1.9k stars, MIT, last commit May 20265176033040 out of 100
#4stockbot-on-groqGroq chatbot answering with TradingView widgets via AI SDK generative UI Live demo ↗ (opens in a new tab)1.5k stars, Apache-2.0, last commit Dec 20254020033024 out of 100
#5assistant-ui-stockbrokerassistant-ui frontend and LangGraph.js stockbroker agent with approval steps281 stars, MIT, last commit Feb 202684700013 out of 100
#6openai-structured-outputs-samplesThree Next.js samples driving UI from schema-constrained OpenAI outputs685 stars, MIT, last commit Dec 2025252400011 out of 100

Momentum, Verified build, Docs and Privacy are not measured yet; their weight goes to the signals shown. A dash means the signal is not scored for that kind of project. Hover a number for its rating in words.

Reviews

145 out of 100

agent-chat-ui

Next.js chat frontend for any LangGraph server with interrupts and artifacts

Live demo ↗ (opens in a new tab)3.2k stars, MIT, last commit Oct 2026

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.

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
245 out of 100

OpenGenerativeUI

Chat interface that answers with 3D models, charts, calculators and maps

2.4k stars, MIT, last commit Oct 2026

Open Intelligent UI is a Next.js chat frontend backed by a Python Deep Agent (FastAPI) that decides per turn whether to reply with text, a native component, or custom HTML/CSS/JS streamed into a sandboxed iframe. A routing model called Jev picks A2UI for basic tables and Open Generative UI for charts, diagrams, calculators and maps. It is built on CopilotKit and AG-UI, with an optional standalone MCP server.

Strengths

  • Generated UI runs in an isolated iframe with a validated host bridge
  • Visitors can supply their own OpenAI and Jev keys, held only in browser memory
  • Optional MCP server with HTTP, stdio and Docker configuration
  • Provider failures are surfaced rather than silently swapped for another model

Weaknesses

  • Needs both an OpenAI key and a TYPESAFE_API_KEY for Jev routing
  • Requires Node 22+, pnpm 9+, Python 3.12+ and uv locally
  • Output format varies per request because the router chooses the renderer
  • No tagged release; no compose file
  • TypeScript, OpenAI chat-latest, Jev jev-latest
  • Needs OpenAI API, Jev (Typesafe) API, USGS map tiles
  • Docker
  • env example file
340 out of 100

agent-ui

Next.js chat frontend for Agno AgentOS with tool calls and reasoning

1.9k stars, MIT, last commit May 2026

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.

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
#424 out of 100

stockbot-on-groq

Groq chatbot answering with TradingView widgets via AI SDK generative UI

Live demo ↗ (opens in a new tab)1.5k stars, Apache-2.0, last commit Dec 2025

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.

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
#513 out of 100

assistant-ui-stockbroker

assistant-ui frontend and LangGraph.js stockbroker agent with approval steps

281 stars, MIT, last commit Feb 2026

A Turborepo with a Next.js 16 frontend on assistant-ui and a LangGraph.js backend defining a stockbroker graph that calls GPT-4o, Financial Datasets and Tavily, with human-in-the-loop approval before trades. The frontend proxies to the LangGraph dev server (port 2024) with an optional LangSmith key, three API keys are needed, and there is no auth beyond LangGraph threads. For teams pairing assistant-ui with LangGraph.js.

Strengths

  • Shows assistant-ui wired to a LangGraph.js graph with interrupts
  • Frontend and backend start together with pnpm dev
  • Biome lint and format configured

Weaknesses

  • Three keyed services: OpenAI, Financial Datasets, Tavily
  • No tests, no auth
  • Demo domain; trading tools are not real brokers
  • Seed shows 281 stars
  • TypeScript, openai, langgraph, assistant-ui
  • Needs openai-api-key, financial-datasets-api-key, tavily-api-key
#611 out of 100

openai-structured-outputs-samples

Three Next.js samples driving UI from schema-constrained OpenAI outputs

685 stars, MIT, last commit Dec 2025

Three small Next.js apps, each with its own README: resume extraction renders structured fields from a model response, generative UI builds components from a JSON-schema output, and conversational assistant combines multi-turn chat, tool calling and generative UI in one flow. All rely on OpenAI Structured Outputs so responses always match the schema. For developers deciding how to bind model JSON to React components.

Strengths

  • Conversational assistant sample is a reasonable base for a schema-driven assistant
  • Each sample is independent; copy one folder
  • Shows the schema-to-component pattern without a framework

Weaknesses

  • Root README has no setup; per-folder READMEs only
  • OpenAI-only
  • No auth, persistence or tests
  • Last commit 2025-12
  • TypeScript, openai
  • Needs openai-api-key

Written from each project's README and checked facts. Spot something wrong? Report it on GitHub (opens in a new tab).