The A2UI roadmap describes the tools we are building around the protocol to help you take a generative UI (gen-UI) agent from its first component to production, and keep improving it after launch.
Shipping a gen-UI agent involves five stages that repeat. You build components, configure your agent to use them, evaluate the results, distribute the agent to your users, and monitor how they respond. What you learn while monitoring feeds the next round of component work, so the stages form a loop.
The diagram below shows that loop. Select a stage to see what is available today and what is planned for it. The A2UI CLI is at the center because we plan for it to cover every stage, so you or your coding agent can run the whole loop from a terminal.
$ a2ui
build
The whole loop, from your coding agent
Stage 01 of 05
Build cross-platform components
Design components once and render them natively on every platform.
Available today
Catalogs and the Basic Catalog, themed by each host framework
Official renderers for React, Lit, Angular, Flutter, SwiftUI, and Jetpack Compose
Universal Web Components and a2ui codegen
On the roadmap
Primitives you style to your design system and describe once
A runtime templating engine that renders them natively on each platform
A secure sandbox for components with shared business logic
Primitives that you style to match your design system and describe declaratively. Today a custom component still needs an implementation on each native platform; described primitives remove that step.
A runtime templating engine that reads a component’s description and renders it natively on each platform.
A secure sandbox for components that need shared business logic, such as validation or pricing rules, where a declarative description is not enough. We will investigate a sandbox that lets you write that logic once and run it safely on every client.
Configure your agents
Our goal is for your agent to know when and how to use each component.
Available today
The skill generator (SkillGenerator) in the Python and TypeScript Agent SDKs builds an A2UI skill from your catalog, with grammar rules for the chosen inference format and the signatures of your components and functions. Because the skill comes from the catalog, it changes when your components change. See Generate the skill.
Official Agent SDK support for decision models, such as Jev from TypeSafe, as an inference format. A decision model answers typed questions about layouts you define in advance instead of generating the component tree token by token, which makes layout decisions up to 80x faster. Fast, reliable A2UI describes the approach, and jev2ui is an open-source example that builds A2UI screens from Jev decisions (try it hosted as Apparite).
Clearer error handling and diagnostics in the skill generator when a catalog or inference format cannot be compiled.
Skill generation in the Dart Agent SDK, which does not support it yet.
Integrations with more agent frameworks.
Evaluate gen-UI quality
Our goal is for you to know whether your agent picks the right components and builds them correctly.
Available today
The A2UI evaluation framework is built on Inspect AI and scores model output against the project’s own datasets in three stages: schema and structure validation, deterministic assertions, and an LLM judge that grades intent and quality. See the evaluation design.
Better tooling for MCP Apps, which is our first focus for distribution. This starts with sharing state between A2UI components and the MCP host and server when A2UI runs inside an MCP App, to match what McpApp already does in the other direction.
Guides and examples for distributing your agent through AI assistants such as Gemini, Claude, and ChatGPT, and through messaging apps such as Microsoft Teams and Slack.
Monitor and evolve
Our goal is for your gen-UI to improve as you learn from your users.
Guidance on which logs to collect from gen-UI experiences, such as rendered surfaces, user actions, errors, and abandoned flows.
Ways to turn those signals into design and component updates, which takes you back to building components.
The A2UI CLI
The A2UI CLI connects the stages. Today it generates typesafe component builders from a catalog with a2ui codegen. We plan to extend it to every stage:
Stage
What the CLI will help with
Build
Scaffold, generate, preview, and publish components and catalogs
Configure
Generate skills and connect catalogs to agents
Evaluate
Validate output and run evaluation suites
Distribute
Package agents for native apps, assistants, and MCP Apps hosts
Monitor
Pull usage and feedback data back into your project
The CLI runs in a terminal and is scriptable, so coding agents can run it directly. The repository also includes an A2UI agent skill that teaches coding agents to work with A2UI. Together, they let a coding agent build a component, wire it into your agent, run evaluations, ship the result, and read the feedback.
Protocol versions
The protocol evolves alongside this tooling. specification/versions.json is the source of truth for version status.