Skip to main content
Back to timeline
ag-ui-protocol/ag-uiSource publication:

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

Synopsis

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.

Source-provided article image: ag-ui-protocol / ag-ui
GitHub Trending

Interpretation

The link between an agent and a front-end application is now described by one open, lightweight, event-based protocol, and the same agent can power a web app, a mobile app, a terminal or Slack. Agents did not fit the request/response model: they stream tokens, call tools mid-response, update shared state, pause for a human and spawn subagents, and every framework did it differently. AG-UI replaces that custom wiring with one bidirectional event stream: the agent emits typed events and any client can render them, no matter which framework built the agent.

The protocol carries one run over a single HTTP endpoint that accepts a RunAgentInput and streams events back. An event encoder picks the content type from the request's accept header, and run-started, text-message-start, text-content, text-message-end and run-finished events are encoded in order into the streaming response. In the example, a roughly 30-line Python agent server paired with a TypeScript client prints the streamed text Hello from AG-UI!, and swapping the server for any supported framework leaves the client unchanged.

The 1.0 specification is frozen and backed by a JSON Schema, and the TypeScript, Python and .NET SDKs are generated from that schema. 1.0 is backwards compatible in both directions: 0.x agents work with 1.0 clients and vice versa. The create-ag-ui-app command-line tool scaffolds a front end, either CopilotKit on Next.js or a terminal client, wired to the chosen agent framework; the generated templates call OpenAI, so a key must be set before running.

Perspective

The demonstrated scope is the protocol specification itself, the TypeScript, Python and .NET SDKs generated from the JSON Schema, the two-way compatibility statement, and a minimal example of a roughly 30-line Python server with a TypeScript client.

The material states that AG-UI is adopted by Google, Microsoft, Amazon and Oracle and built into most agent frameworks, but the list of frameworks is not fully given in the material; the two-way compatibility and the SDK generation appear as statements from the releasing party, and the material gives no corresponding compatibility test results.