Skip to main content
Search

# AG-UI protocol

2 related articles

Subscribe to updates
  1. AG-UI 1.0 freezes its spec: one bidirectional event stream now carries the agent-to-interface link

    AG-UI has reached version 1.0, fixing the connection between AI agents and user-facing applications as a single bidirectional event stream: the agent emits typed events and any client can render them, so each framework no longer needs its own wiring. Agents did not fit the request/response model, because they stream tokens, call tools mid-response, update shared state, pause for a human and spawn subagents, and every framework did this differently. The 1.0 specification is frozen and backed by a JSON Schema, the TypeScript, Python and .NET SDKs are generated from it, and 1.0 is backwards compatible in both directions with 0.x.

  2. AG-UI brings agents into user-facing apps: about 16 standard event types unify both ends and work over any event transport

    AG-UI is an open, lightweight, event-based protocol that standardizes how AI agents connect to user-facing applications. Previously there was no shared convention for wiring an agent into an interface; AG-UI has agent backends emit events matching one of about 16 standard event types during execution and accept a few simple inputs, while a middleware layer adapts to any event transport such as SSE, WebSockets or webhooks. It grew out of CopilotKit's early partnership with LangChain and CrewAI, ships under the MIT license, and comes with a reference HTTP implementation and a default connector.

You’re all caught up