ref.copilotkit.ag-ui · implementation
AG-UI Protocol
AG-UI is an open, bidirectional, event-based transport protocol for agent-to-frontend communication: streaming state, multimodality, typed shared state, tool events, cancel/resume, and generative UI payloads. It explicitly distinguishes transport from A2UI UI description. The protocol is evolving rapidly, so this record uses a 30-day review cadence and the canonical AG-UI protocol owner rather than the former generic CopilotKit URL.
https://docs.ag-ui.com/introduction
What this source teaches
- Define ordered event semantics, reconnect/idempotency, and partial-failure handling for every AG-UI integration — the protocol governs transport reliability, not UI composition.
- Cancellation and resume must be first-class in every streaming UI surface backed by AG-UI: cancel must be keyboard-reachable and immediately effective.
- Shared-state conflict resolution and accessible streaming-announcement behavior (live regions, partial-output labelling) must be explicitly designed, not assumed from the transport.
- Distinguish AG-UI transport from A2UI UI description: AG-UI carries events and state, A2UI describes component schemas — they are complementary layers, not alternatives.
Where AwesomeDS applied it
rule.ai.generative-boundaries— Agents compose approved contractsrule.ai.ux-streaming-contract— Treat streaming as semantic asynchronous state
Implementations and artifacts
No directly linked artifacts.
Caveats & anti-imitation
Transfer ordered event semantics, cancel/resume, and shared-state conflict patterns; do not conflate AG-UI transport with the UI schema or product policy layers.