AG-UI
An event-based protocol for connecting agent runtimes to user-facing applications with streaming, state, tools, and human interaction.
A field guide to the protocols, declarative specifications, renderers and host surfaces behind interfaces that agents can shape at runtime.
RUN_STARTEDagent → clientTEXT_MESSAGE_CONTENTstreamingTOOL_CALL_STARTrender_cardUSER_ACTIONapprovedThese technologies compose across layers. Compare their responsibilities before comparing their APIs.
How do runs, messages, tools and state move?
How is UI intent constrained and rendered?
What ships the product experience?
Seven source-backed guides using the same decision framework—without a winner-takes-all ranking.
An event-based protocol for connecting agent runtimes to user-facing applications with streaming, state, tools, and human interaction.
A declarative, portable UI format that lets agents describe updatable interfaces rendered through trusted client-side component catalogs.
A streaming-first Generative UI framework built around a compact language, React runtime, component libraries, prompt generation, and chat surfaces.
A Generative UI framework where models produce predictable JSON specifications constrained by developer-defined components and actions.
An emerging declarative JSON UI concept documented by CopilotKit, without a separately verified first-party OpenAI specification repository.
An official MCP extension for serving sandboxed interactive HTML interfaces from MCP servers into compatible conversational hosts.
A frontend and runtime platform for agentic applications, Generative UI patterns, and integrations built around the AG-UI ecosystem.
Four constraints produce a transparent recommendation you can audit.
Boundary to verify: json-render constrains output to registered components and AG-UI supplies the interaction stream. Catalog design and validation remain your responsibility.
Boundary to verify: If interoperability matters more than framework ergonomics, evaluate A2UI; if the UI must live inside an AI host, evaluate MCP Apps.
Three focused routes for understanding the stack, making an architecture decision, and operating it safely.
Build a durable mental model of transport, declarative UI, embedded surfaces, and implementation frameworks.
Start path →02intermediate · 60 minTurn product constraints into an explainable combination of protocols, specifications, renderers, and host surfaces.
Start path →03advanced · 75 minDesign trust boundaries, event tracing, approval gates, recovery paths, and evaluation signals for production Generative UI.
Start path →