R049 · Agent principles and patterns › Agent interaction protocols

A2UI 1.0: agents answer with your app's own UI components

Read the original

agent-protocolsagent-architecturehuman-oversight

Sources: Shubham Saboo's LinkedIn post announcing the 1.0 release (2026-11-11); A2UI v1.0 specification; earlier Google Developers Blog posts on the launch and v0.9.

In one paragraph

A2UI is an open (Apache 2.0) protocol, started by Google, that lets an agent reply with interactive interface instead of text: forms, charts, pickers, approval cards. The agent sends a stream of declarative JSON describing what to show, and the host app renders it with its own native components from a catalog the app controls. The agent can't ship code or use components it wasn't given, so screens match the product and the attack surface stays small. Version 1.0 is the first stable release. It ships renderers for React, Angular, Flutter and SwiftUI, agent SDKs for Python, TypeScript and Dart, and built-in accessibility; native Android is still to come. Announced adopters include Atlassian (decision cards inside Jira work items), Alation, ByteDance's Lynx framework, Bloomberg, and Google's own Gemini Notebook and Gemini Enterprise. The positioning: MCP connects agents to tools, A2A connects agents to each other, and A2UI covers what the user actually touches.

How the protocol works

Where it sits among agent UI standards

A2UI describes what to render, declaratively, from a trusted catalog. Event protocols such as AG-UI (R034) describe the run itself: streamed text, tool calls, state deltas and interrupts. MCP Apps embed tool-provided HTML. The approaches can be combined, for example A2UI surfaces carried over an event stream. They differ mainly in who owns the rendering code and how much the agent can inject.

Tradeoffs and failure modes

Review checklist

Connections

See R049 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.