AG-UI: the Agent-User Interaction Protocol. Bring Agents into Frontend Applications.
★ 18,242⑂ 1,883👁 99⑃ 2,323● 884▤ 78
+752
日增长
18,242
stars
1,883
forks
99
watchers
2,323
prs
884
issues
78
releases
README
AG-UI: The Agent-User Interaction Protocol AG-UI is an open, lightweight, event-based protocol that standardizes how AI agents connect to user-facing applications. Built for simplicity and flexibility, it enables seamless integration between AI agents, real time user context, and user interfaces. --- !MIT !Discord Join our Discord → Read the Docs → Go to the AG-UI Dojo → Follow us → 🚀 Getting Started Create a new AG-UI application in seconds: bash npx create-ag-ui-app my-agent-app Useful Links: - The AG-UI Dojo - Build AG-UI-powered applications(Quickstart) - Build new AG-UI framework integrations (Quickstart) - Book a call to discuss an AG-UI integration with a new framework - Join the Discord Community What is AG-UI? AG-UI is an open, lightweight, event-based protocol for agent-human interaction, designed for simplicity & flexibility: - During agent executions, agent backends emit events _compatible_ with one of AG-UI's ~16 standard event types - Agent backends can accept one of a few simple AG-UI compatible inputs as arguments AG-UI includes a flexible middleware layer that ensures compatibility across diverse environments: - Works with any event transport (SSE, WebSockets, webhooks, etc.) - Allows for loose event format matching, enabling broad agent and app interoperability It also ships with a reference HTTP implementation and default connector to help teams get started fast. Learn more about the specs → Why AG-UI? AG-UI was developed based on real-world requirements and practical experience building in-app agent interactions. Where does AGUI fit in the agentic protocol stack? AG-UI is complementary to the other 2 top agentic protocols - MCP gives agents tools - A2A allows agents to communicate with other agents - AG-UI brings agents into user-facing applications 🚀 Features - 💬 Real-time agentic chat with streaming - 🔄 Bi-directional state synchronization - 🧩 Generative UI and structured messages - 🧠 Real-time context enrichment - 🛠️ Frontend tool integration - 🧑💻 Human-in-the-loop collaboration 🛠 Supported Integrations AG-UI was born from CopilotKit's initial partnership with LangChain 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. Frameworks | Framework | Status | AG-UI Resources | | ------------------------------------------------------------------ | ------------------------ | -------------------------------------------------------------------------------- | | Built-in Agent | ✅ Supported | ➡️ Docs | 🤝 Partnerships | Framework | Status | AG-UI Resources | | --
Top issues
#510Add React Native Client to AG-UI21 comments · 2025-10-09#494Add Swift SDK13 comments · 2025-10-07#733A user-triggered stopGeneration causes a server error (ECONNRESET) instead of performing a clean abort.11 comments · 2025-11-24#231Support MCP elicitation11 comments · 2025-07-29#2256sdks/community/rust has no code owner and open Rust PRs aren't moving10 comments · 2026-07-28#2862[Feature]: Surface ADK citations and grounding sources on assistant message metadata in the ADK middleware9 comments · 2026-09-29#2241[Bug]: ADK converter drops valid binary data when `id` or `url` is also present9 comments · 2026-07-24#868AGUI not streaming in Microsoft Edge browser (Mac & Windows)9 comments · 2025-12-24
Discussions
#3402Which event should carry a widget that a server tool produces: a tool call, `ACTIVITY_SNAPSHOT` or `CUSTOM`?0 comments · 2026-11-15#3309Proposal: define what the resume.metadata tamper-proof signature covers — a WYSIWYS consent binding for rendered surfaces3 comments · 2026-11-03#2845A2UI with a Python (Strands) agent and non-CopilotKit clients: is a TypeScript `A2UIMiddleware` tier required?3 comments · 2026-09-28#2792AG-UI 1.0 is officially released0 comments · 2026-09-18#2790Where does agent authority sit relative to AG-UI, MCP and A2A?2 comments · 2026-09-18#2723Material 3 Expressive React client for AG-UI0 comments · 2026-09-11#2608AG-UI is heading to 1.0 - the draft specification is live3 comments · 2026-09-02#2564Spec clarification: what should `RUN_FINISHED.outcome` be when a run ends with unresolved client-side tool calls?1 comments · 2026-08-28
Latest release
Release 2026-11-13 release/2026-11-13 2026-11-13Packages Published TypeScript (npm) - published at 21:01:19 UTC | Package | Version | Install | |---------|---------|--------| | @ag-ui/langgraph | 0.0.46 | npm install @ag-ui/[email protected] | @ag-ui/[email protected] - Read LangGraph's native Interrupt.response_schema field (langgraph = 1.2.12), falling back to value-level responseSchema/response_schema keys. - Unwrap LangChain-serialized ToolMessage outputs under kwargs on tool end so tool calls and results emit correctly. - Skip on_tool_end outputs with no tool call id instead of throwing or emitting events with an undefined id. - Decl