AG-UI 1.0: A Frozen, Open Protocol For Streaming AI Agents to Any Frontend
Frontend teams can stop writing a custom adapter for every agent framework; one typed event stream handles streaming text, tool calls, state, and human approval across web, mobile, terminal, and Slack. AG-UI's freeze at 1.0 gives a stable target, but teams should check how deeply their chosen framework is integrated before committing.
AG-UI is an open, MIT-licensed protocol that standardizes how AI agents talk to user-facing applications. Instead of a single request-response cycle, agents emit a typed event stream: streaming text, tool calls, shared state updates, reasoning traces, interrupts for human approval, and subagent runs. Any compatible frontend can render those events, so one agent works across the web, mobile, a terminal, or Slack without per-framework adapters. The protocol sits alongside MCP and A2A: MCP provides tools, A2A handles agent-to-agent, and AG-UI covers agent-to-user.
AG-UI 1.0 is frozen with JSON Schema support and backward compatibility between 0.x and 1.0. It defines 31 event types across eight families (though a wildcard in the reasoning family means the README's count includes expansions not individually listed). Transport is HTTP+SSE or HTTP+Protobuf. State sync uses snapshot and delta events with JSON Patch for partial updates. Human-in-the-loop ends a run with an interrupt event; the next run resumes from there, so servers don't hold long-lived connections. Official SDKs cover TypeScript, Python, and .NET, with community SDKs for Kotlin, Go, Java, Dart, Rust, Ruby, C++, and Swift. The project is initiated by CopilotKit and reports adoption by Google, Microsoft, Amazon, and Oracle, with integrations for LangChain, CrewAI, and many other frameworks.
The main caveats: not every framework has native integration, and ready-to-use frontend components lean toward CopilotKit's ecosystem. The spec is frozen, so new features wait for draft specs. This analysis is based on the README and repo structure, not a live run.
Ending a run with interrupt instead of holding a connection is a pragmatic design that lets servers free resources between turns, at the cost of re-sending context on resume.
Because AG-UI is initiated by CopilotKit, the protocol is open but the ready-made frontend components lean on CopilotKit's ecosystem, so teams should weigh that when choosing a stack.
The spec's freeze at 1.0 gives stability but pushes new features to draft specs; adoption depth varies across frameworks, as the README itself notes via middleware recommendations.
The event model's eight families cover everything from token streaming to subagents, so a frontend can treat any agent framework as a black box that emits a known event sequence.