Loading content
An event-streamed protocol standardizing how an agent talks to a front-end — token streams, tool-call states, and human input — so any UI can host any agentic backend. Scope: Agent ↔ User / UI. The key architectural concerns are the boundary being bridged, the trust model and interoperability with existing agents and services.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
AG-UI makes the events by which a user interface exposes and controls an agent run interoperable.
The project emerged at CopilotKit in 2024 from the need to exchange agent state, messages, and human interventions between agent backends and front ends.
Imagine a shared stage direction: the agent reports each entrance, and the interface renders it live.
The task the concept fulfills.
A constraint or prerequisite to consider.
How the concept fits into a larger system.
AG-UI fits live interfaces that expose agent state, tool calls, and human interventions. Its value comes from shared events; the specification does not define a domain UI and requires compatible implementations.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.