ref.a2ui.protocol · implementation
A2UI — Declarative Agent-to-UI Protocol
A2UI is an open, framework-independent declarative JSON UI protocol for agent-generated interfaces. It governs the generated-UI schema and rendering layer through a trusted client component catalog, incremental updates, and no arbitrary generated code. The official project describes v0.9.1 as production, v1.0 as a release candidate, and the project as early-stage. The old google/A2UI repository redirects to a2ui-project/a2ui, so the publisher is recorded as the A2UI project. Review frequently until 1.0 stabilizes.
What this source teaches
- Define an AwesomeDS component catalog schema with explicitly allowed component types, props, and action schemas — only catalog-registered components may be generated.
- Require semantic-token-only values in generated UI; validator must reject raw colors, spacing, z-index, or arbitrary CSS from agent output.
- Provide a static fallback for every generated surface and define renderer/version compatibility and an expiry/review date for each generated-surface manifest.
- Mark all A2UI-derived patterns as experimental until the v1.0 protocol stabilizes.
Where AwesomeDS applied it
Implementations and artifacts
No directly linked artifacts.
Caveats & anti-imitation
Transfer the declarative component catalog schema pattern and semantic-token-only constraint; do not assume v0.9.x API stability or use A2UI as a finished production standard.