AG-UI Overview - Agent User Interaction Protocol
On this page
- The Agent–User Interaction (AG-UI) Protocol
- Agentic Protocols
- Building blocks (today & upcoming)
- Why Agentic Apps need AG-UI
- The requirements of user‑facing agents
- AG-UI in Action
- Supported Integrations
- Direct to LLM
- Agent Framework - Partnerships
- Agent Framework - 1st Party
- Agent Framework - Community
- Agent Interaction Protocols
- Infrastructure / Deployment
- Specification (standard)
- SDKs
- Clients
- Quick Start
- Explore AG-UI
- Resources
- Contributing
- Support and Feedback
Get Started
AG-UI Overview
The Agent–User Interaction (AG-UI) Protocol
AG-UI is an open , lightweight , event-based protocol that standardizes how AI agents connect to user-facing applications. AG-UI is designed to be the general-purpose, bi-directional connection between a user-facing application and any agentic backend. Built for simplicity and flexibility, it standardizes how agent state, UI intents, and user interactions flow between your model/agent runtime and user-facing frontend applications—to allow application developers to ship reliable, debuggable, user‑friendly agentic features fast while focusing on application needs and avoiding complex ad-hoc wiring.


Agentic Protocols
Confused about “A2UI” and “AG-UI”? That’s understandable! Despite the naming similarities, they are quite different and work well together. A2UI is a generative UI specification - allowing agents to deliver UI widgets, where AG-UI is the Agent↔User Interaction protocol - which connects an agentic frontend to any agentic backend. Learn more
AG-UI is one of three prominent open agentic protocols.
Layer| Protocol / Example| PurposeAgent ↔ User Interaction| AG-UI (Agent–User Interaction Protocol)| The open, event-based standard that connects agents to user-facing applications — enabling real-time, multimodal, interactive experiences.Agent ↔ Tools & Data|MCP (Model Context Protocol)| Open standard (originated by Anthropic) that lets agents securely connect to external systems — tools, workflows, and data sources.Agent ↔ Agent|A2A (Agent to Agent)| Open standard (originated by Google) which defines how agents coordinate and share work across distributed agentic systems.
Building blocks (today & upcoming)
Streaming chat
Multimodality
Generative UI, static
Generative UI, declarative
Shared state
Thinking steps
Frontend tool calls
Backend tool rendering
Interrupts (human in the loop)
Sub-agents and composition
Agent steering
Tool output streaming
Custom events
Why Agentic Apps need AG-UI
Agentic applications break the simple request/response model that dominated frontend-backend development in the pre-agentic era: a client makes a request, the server returns data, the client renders it, and the interaction ends.
The requirements of user‑facing agents
While agents are just software, they exhibit characteristics that make them challenging to serve behind traditional REST/GraphQL APIs:
- Agents are long‑running and stream intermediate work—often across multi‑turn sessions.
- Agents are nondeterministic and can control application UI nondeterministically.
- Agents simultanously mix structured + unstructured IO (e.g. text & voice, alongside tool calls and state updates).
- Agents need user-interactive composition : e.g. they may call sub‑agents, often recursively.
- And more…
AG-UI is an event-based protocol that enables dynamic communication between agentic frontends and backends. It builds on top of the foundational protocols of the web (HTTP, WebSockets) as an abstraction layer designed for the agentic age—bridging the gap between traditional client-server architectures and the dynamic, stateful nature of AI agents.
AG-UI in Action
Your browser does not support the video tag.
You can see demo apps of the AG-UI features with the framework of your choice, with preview, code, and walkthrough docs in the AG-UI Dojo
Supported Integrations
AG-UI was born from CopilotKit’s initial partnership with LangGraph and CrewAI - and brings the incredibly popular agent-user-interactivity infrastructure to the wider agentic ecosystem. 1st party = the platforms that have AG‑UI built in and provide documentation for guidance.
Direct to LLM
Framework| Status| AG-UI Resources
Direct to LLM| Supported| Docs
Agent Framework - Partnerships
Framework| Status| AG-UI Resources
LangGraph| Supported| Docs, Demos CrewAI| Supported| Docs, Demos
Agent Framework - 1st Party
Framework| Status| AG-UI Resources
Microsoft Agent Framework| Supported| Docs, Demos Google ADK| Supported| Docs, Demos AWS Strands Agents| Supported| Docs, Demos AWS Bedrock AgentCore| Supported| Docs Mastra| Supported| Docs, Demos Pydantic AI| Supported| Docs, Demos Agno| Supported| Docs, Demos LlamaIndex| Supported| Docs, Demos AG2| Supported| Docs Demos AWS Bedrock Agents| In Progress| –
Agent Framework - Community
Framework| Status| AG-UI Resources
OpenAI Agent SDK| In Progress| – Cloudflare Agents| In Progress| –
Agent Interaction Protocols
Protocol| Status| AG-UI Resources| Integrations
A2A Middleware| Supported| Docs| Partnership
Infrastructure / Deployment
Platform| Status| AG-UI Resources| Integrations
Amazon Bedrock AgentCore| Supported| Docs| 1st Party
Specification (standard)
Framework| Status| AG-UI Resources
Oracle Agent Spec| Supported| Docs, Demos
SDKs
SDK| Status| AG-UI Resources| Integrations
Kotlin| Supported| Getting Started| Community Golang| Supported| Getting Started| Community Dart| Supported| Getting Started| Community Java| Supported| Getting Started| Community Rust| Supported| Getting Started| Community .NET| In Progress| PR| Community Nim| In Progress| PR| Community Flowise| In Progress| GitHub Source| Community Langflow| In Progress| GitHub Source| Community
Clients
Client| Status| AG-UI Resources| Integrations
CopilotKit| Supported| Getting Started| 1st Party Terminal + Agent| Supported| Getting Started| Community React Native| Help Wanted| GitHub Source| Community
Quick Start
Choose the path that fits your needs:
Build agentic applications
Build agentic applications powered by AG-UI compatible agents.
Build new AG-UI integrations
Build integrations for new agent frameworks, custom in-house solutions, or use AG-UI without any agent framework.
Build AG-UI compatible clients
Build new clients for AG-UI-compatible agents (web, mobile, slack, messaging, etc.)
Explore AG-UI
Dive deeper into AG-UI’s core concepts and capabilities:
Core architecture
Understand how AG-UI connects agents, protocols, and front-ends
Events
Learn about AG-UI’s event-driven protocol
Resources
Explore guides, tools, and integrations to help you build, optimize, and extend your AG-UI implementation. These resources cover everything from practical development workflows to debugging techniques.
Developing with Cursor
Use Cursor to build AG-UI implementations faster
Troubleshooting AG-UI
Fix common issues when working with AG-UI servers and clients
Contributing
Want to contribute? Check out our Contributing Guide to learn how you can help improve AG-UI.
Support and Feedback
Here’s how to get help or provide feedback:
- For bug reports and feature requests related to the AG-UI specification, SDKs, or documentation (open source), please create a GitHub issue
- For discussions or Q&A about AG-UI, please join the Discord community
Was this page helpful?
YesNo
⌘I
Powered byThis documentation is built and hosted on Mintlify, a developer documentation platform