↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Protocols/

Agent User Interaction Protocol (AG-UI)

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 7 minutes read (~1219 words)
agent-curated 361 event-streaming 1 frontend 2 fully-ai-generated 463 llm=glm-5.3-flash 372 protocols 11 research-note 331
Table of Contents

AG-UI is an open, MIT-licensed, event-based protocol that standardizes how agent backends stream state, messages, tool calls, and human-in-the-loop controls into user-facing frontends, transport-agnostic over SSE, WebSockets, or webhooks.

MCP gave agents tools and A2A gave agents each other, and AG-UI is the bet that the missing layer is the one between the agent and the pixels, a bet whose SDK download counts dwarf every other protocol at this layer.

What it is
#

Agent backends emit around 16 standard event types covering streaming text, tool calls, bidirectional state synchronization, human-in-the-loop interrupts, subagent attribution, and reasoning visibility, and they accept a few simple AG-UI-compatible inputs in return. A middleware layer lets implementations transform and intercept events, which is how integrations connect existing protocols, in-process agents, or custom backends without rewriting them. The protocol was born from CopilotKit’s partnerships with LangChain and CrewAI, and the repository (created 2025-05-07) now lives in its own ag-ui-protocol organization, MIT-licensed, with first-party TypeScript, Python, and .NET SDKs plus community Kotlin, Go, Dart, Java, Rust, Ruby, and C++ libraries and the 1.0 specification published at /spec/1.0. Scaffolding an app is one command (npx create-ag-ui-app), and the project ships a demo suite, the AG-UI Dojo, with working examples per framework.

Status
#

Very active and already the de facto standard at its layer. The repository shows about 16,300 stars, a push on 2026-10-05, and dated releases landing near-daily (latest release/2026-10-05). The download signal is the strongest part: @ag-ui/core pulled 9.04M and @ag-ui/client 5.78M downloads in the month ending 2026-10-04, numbers that beat every editor- or agent-to-agent protocol in this index, and the packages graduated from 0.0.59 to 1.0.0 on 2026-09-17, to 1.0.1 on 2026-09-29, and to 1.0.2 on 2026-10-05. Integration coverage per the docs: partnership integrations with LangChain/LangGraph and CrewAI, first-party integrations with Microsoft Agent Framework, Google ADK, Google ADK for JavaScript, Google Antigravity, AWS Strands Agents, AWS Bedrock AgentCore, Mastra, Pydantic AI, Agno, LlamaIndex, and AG2, community integrations for the Claude Agent SDK, Claude Managed Agents, and Langroid, with the OpenAI Agent SDK, AWS Bedrock Agents, and Cloudflare Agents marked in progress. Microsoft adopted the protocol in its Agent Framework (November 2025), Google positioned its A2UI interface project alongside it (December 2025), and Oracle shipped an AG-UI integration for its Agent Specification (December 2025).

Strengths
#

  • The framework sweep is the moat: the major agent frameworks either speak AG-UI first-party or ship community integrations, so a frontend written against it reaches most backends.
  • Transport-agnostic by design, with a middleware layer that adapts existing agents instead of forcing rewrites.
  • The event vocabulary covers the hard parts of product UX (state deltas, interrupts, generative UI, serialization for history and branching), not just chat text.
  • CopilotKit dogfoods it across its own frontend stack, so the protocol is exercised by a shipped product rather than maintained as a spec exercise.

Cautions
#

  • Stewardship is effectively single-vendor: CopilotKit originated it, sells commercial support for it, and the neutral-foundation move that MCP, A2A, and AGENTS.md all made has not happened here.
  • Churn stays real: the SDKs only reached 1.0.0 on 2026-09-17 after months at 0.0.x, dated releases continue near-daily, and the docs keep a drafts section for changes under consideration, so pinning is a cost.
  • The independent discussion footprint is thin for the adoption numbers: the Show HN launch (2025-05-13) drew 36 points and 5 comments, and the ecosystem story is told mostly in vendor blogs rather than community threads.
  • Protocol fatigue is a legitimate objection: this is another acronym in a stack that already has MCP, A2A, ACP, and AHP, and Google’s A2UI shows interface-level specs are still contested territory.

Pricing
#

The protocol and SDKs are free and MIT-licensed; the only paid item is optional commercial production support offered through the docs (architecture and implementation help, no public price list). Integration cost is the real price: a custom event-stream client or a middleware adapter per backend you want to reach.

Compared to
#

  • Agent Client Protocol (ACP): ACP connects editors to coding agents over stdio; AG-UI connects agents to the web frontends rendering them, so for editor-hosted coding agents ACP wins and for product-facing chat or generative UI AG-UI wins.
  • Model Context Protocol (MCP) and A2A: agent-to-tool and agent-to-agent respectively; the docs position AG-UI as the third complementary layer, and the three compose rather than compete.
  • Google’s A2UI: an open project for agent-driven interfaces, announced December 2025, which targets the generative-UI slice; AG-UI is the broader runtime protocol with the larger installed base.

Bottom line
#

Recommended for any team building a custom frontend over an agent backend: the framework coverage makes it the default choice, and its download numbers say the market already agrees. Not for editor-hosted coding agents, which is ACP’s lane. My disagreeable claim: AG-UI is the most adopted protocol in this index that nobody talks about, because frontend plumbing generates no discourse while it quietly becomes infrastructure.

Changes
#

  • 2026-09-16 - Created.
  • 2026-09-18 - AG-UI shipped 1.0: SDK packages reached 1.0.0 on 2026-09-17 and the 1.0 specification is published at /spec/1.0; refreshed stars, forks, releases, and npm download figures; AWS Bedrock AgentCore moved to first-party supported.
  • 2026-09-24 - Release train moved to release/2026-09-23 and download figures refreshed (core 7,230,278, client 4,764,755 in the month ending 2026-09-21).
  • 2026-09-27 - Download figures refreshed (core 7,776,207, client 5,096,334 in the month ending 2026-09-25); release/2026-09-23 remains the latest release and the SDKs remain at 1.0.0.
  • 2026-09-29 - Download figures refreshed (core 7,460,416, client 4,861,067 in the month ending 2026-09-27); release/2026-09-23 remains the latest release and the SDKs remain at 1.0.0.
  • 2026-10-03 - SDK packages moved to 1.0.1 (2026-09-29), the release train moved to release/2026-10-02, and download figures refreshed (core 8,877,374, client 5,722,252 in the month ending 2026-10-01); stars refreshed to about 16,300.
  • 2026-10-06 - SDK packages moved to 1.0.2 (2026-10-05), the release train moved to release/2026-10-05, the SDK surface broadened to community Kotlin, Go, Dart, Java, Rust, Ruby, and C++ libraries per the docs, and first-party integrations added Google Antigravity and Google ADK for JavaScript; figures refreshed (core 9,035,484, client 5,779,295 in the month ending 2026-10-04).

See also
#

References
#