Most agent news is about plumbing you never see. A2UI is the exception, because it is about the part you do see. In December 2025 Google opened a project called A2UI that lets an agent generate an interface itself, a booking form, a comparison table, an interactive chart, and hand it to your app to draw. It points at a near future where the agent does not just answer a question, it composes the screen the answer needs.
What Google announced
A2UI, introduced at developers.googleblog.com/introducing-a2ui-an-open-project-for-agent-driven-interfaces, is an open format for agent-generated user interfaces. Instead of shipping code, an agent sends a declarative description of an interface, which your application renders using its own components. Google frames the reason this now matters in terms of where agents live:
We are entering the era of the multi-agent mesh. Agents from Google are talking to agents from Cisco, IBM, SAP, and Salesforce to solve complex tasks.
In that mesh, the agent doing the work is often remote and untrusted, running on someone else's server. It cannot be handed the keys to your interface, so A2UI keeps what it sends inert:
Orchestrator agents and remote A2A subagents can all generate UI layouts which are securely passed as messages, not as executable code.
The project is early, published at version v0.8 with working client libraries for Flutter, Web Components, and Angular. What it establishes is a direction, not a finished product.
In plain English
Today an agent that needs a date, a time, and a party size drags you through a clumsy text exchange: what day, what time, sorry that slot is taken, when are you free. A2UI lets the agent skip the back-and-forth and produce a small booking form instead, a date picker and a time selector, rendered right where the conversation is.
The clever part is how that stays safe. The agent does not send a program to run. It sends a blueprint, a plain description that says "put a date field here, a dropdown there," referencing only components from a catalog your app has pre-approved. Your application maps that blueprint onto its own trusted, native building blocks. Because the payload is data and not code, a remote agent you do not fully trust can propose an interface without ever being handed the ability to execute anything on your page. The result inherits your app's own styling, so an agent-drawn screen still looks like it belongs to you.
Why this matters for your business
The screen is becoming something an agent assembles on the fly, and that changes where design work lives. If agents are going to compose interfaces from your components, someone has to define that catalog: which building blocks exist, how they look, how they behave, what an agent is and is not allowed to render. That is a design system with a new job, a set of trusted parts an agent can draw from without wandering off-brand or off-spec.
This is not a problem you solve with a chatbot widget. An agent-drawn interface that pulls from a thin or inconsistent catalog will feel generic and disjointed, the way a page stitched from mismatched parts always does. The businesses whose agent experiences feel considered will be the ones that treated the component catalog as a deliverable, not an afterthought. A2UI at v0.8 is early enough that there is time to get ahead of it, and short enough runway that starting late will show.
Where Trinzik fits
This one is forward-looking, and it lands squarely in what an agency does. When agents render interfaces, the trusted component catalog and the design system behind it are the product, and building those is craft work: defining the parts, making them coherent, and wiring them to grounded content so what the agent draws is both on-brand and accurate. Our Apex Domain Agents work already treats a client's site as the source of truth an agent answers from; extending that to the interface the agent composes is the same discipline applied one layer up.
The underlying technology is standard protocols plus a design system built for agents to use, which is exactly the intersection we work at. A2UI is a signal of where agent experiences are heading, and the catalog is the part worth building before you need it.
If you want to be ready for the moment agents start composing your interface, not just answering in it, get in touch.
Questions this raises
What is A2UI?
A2UI is an open format Google introduced in December 2025 for agent-generated user interfaces. Instead of an agent sending executable code, it sends a declarative description of an interface, such as a booking form or comparison table, which the receiving application renders using its own pre-approved components, so the result inherits that app's native styling.
Is A2UI executable code that runs on my site?
No. Google specifies that orchestrator agents and remote A2A subagents generate UI layouts which are securely passed as messages, not as executable code. A remote agent can propose what an interface should contain without ever being handed the ability to execute anything on the page that renders it.
What does Google mean by the 'multi-agent mesh'?
The multi-agent mesh is Google's term for an environment where agents built by different companies routinely talk to each other to complete a task, with Google's own example being agents from Google, Cisco, IBM, SAP, and Salesforce collaborating. A2UI is designed for that setting, where the agent generating an interface is often remote and not fully trusted.
Sources
- Introducing A2UI: An open project for agent-driven interfaces · Google for Developers Blog, December 15, 2025
- a2ui.org quickstart and documentation
- AG-UI protocol