Article / 13
A2UI 1.0 with React and Your Own Design System
See how generative UI works with A2UI 1.0. Try a React demo, inspect its custom catalog and JSON, and find the official A2UI GitHub repository.
Try the A2UI React demo
Confirm the ticket, inspect the JSON, and switch themes to compare the same surface.
Preparing ticket preview…
Google released A2UI 1.0 on November 11, 2026. A2UI is an open protocol for sending interactive UI from an agent to an app. In the ticket demo, React renders a custom card from an A2UI message. Try confirming the ticket and switching themes to see which parts come from the protocol and which parts belong to the host app. Read Google's A2UI 1.0 announcement.
A2UI GitHub repository
The official A2UI GitHub repository is a2ui-project/a2ui. Start with the A2UI 1.0 protocol specification to check the wire format, GitHub Releases to find release notes, and the client integration guide to connect a renderer. The protocol version and the npm package version follow separate version numbers.
What is generative UI?
Generative UI is an interface that an AI system selects or assembles at runtime to fit a user's task. An agent might show a comparison when someone asks about prices, a date picker when they need to book an appointment, or an approval card when it needs confirmation. The user can then act directly in the interface.
A2UI is one way to implement generative UI. The agent sends a structured description with component IDs, data and actions. The host app maps that description to components it has registered. In this demo, saved messages stand in for the agent so you can reproduce the same interaction locally. Explore generative UI approaches.
What changed in A2UI 1.0?
- Inline surfaces. A
createSurfacemessage can include the initial components and data model. The ticket demo uses this to render the entire first card from a single message. - Catalog mixing. A surface can combine components from several registered catalogs. The
@catalogIdproperty selects a catalog for an individual component. - Two-way function calls. The renderer and agent can call registered functions on each other. The ticket demo uses an ordinary
actionevent followed by a data update. - Accessibility and extensions. The protocol defines accessibility and metadata fields. The client still implements the actual semantics and keyboard behavior.
Check the official message reference when adapting an older v0.8 or v0.9.1 example. In particular, 1.0 uses "version": "1.0" and @path for a data binding.
Run the A2UI React example
In an npm-based React TypeScript project, pin the official SDKs and match the demo's two overrides for the upstream Markdown adapter.
npm pkg set 'overrides.@a2ui/markdown-it.@a2ui/web_core=0.15.0'
npm pkg set 'overrides.@a2ui/markdown-it.dompurify=3.4.17'
npm install @a2ui/react@0.15.0 @a2ui/web_core@0.15.0 zod@3.25.76
Save these four files in the same directory, then import the demo component and render <A2uiTicketDemo />. The example uses JSON imports and CSS modules. You can run it in Next.js or a Vite React TypeScript project.
- A2uiTicketDemo.tsx connects the official message processor to the React surface and registers the card.
- catalog.json defines the
TicketCardcontract. - messages.json contains the initial surface and the confirmation response as two separate protocol messages.
- ticket.module.css defines the two host themes.
- Example README has setup and replay instructions.
How the custom catalog works
The catalog declares TicketCard and its permitted properties. createSurface.catalogId selects that catalog, and the React host registers a matching component under the same ID. The wire payload binds status to /ticket/status and confirmed to /ticket/confirmed.
When you confirm the ticket, the renderer emits confirm_ticket with the resolved ticket ID. The local handler plays the role of the agent and sends updateDataModel. The status and button change because the card reads bound values. In your app, send the action to your backend and authorize the requested change before sending back a data update. A2UI guide to defining a catalog.
Apply your design system
- Start with your own
DESIGN.mdor download AuraUI's Linear Design MD. Choose the colors, typography and spacing your component needs. - Map the visual rules to host theme variables. The dark preview maps the capture's background, surface and yellow accent to the canvas, card and confirmation button.
- Decide which controls the agent can compose. Declare those controls and their allowed properties in the catalog. Register their React implementations with the renderer.
- Replay the same JSON with both themes. Check that labels, focus and status changes still work. Change the catalog when the component contract changes, and change the theme when its appearance changes.
Browse AuraUI's Design MD library for more visual references or return to the A2UI resource page for the upstream source and related docs.