A2UI: A Protocol for Agent-Driven Interfaces

#1

Post by makeramen » Tue, Dec 16, 2025, 9:16 AM UTC

A2UI: A Protocol for Agent-Driven Interfaces
a2ui.org

Re: A2UI: A Protocol for Agent-Driven Interfaces

#2

Post by tasoeur » Tue, Dec 16, 2025, 10:19 AM UTC

In an ideal world, people would be implementing UI/UX accessibility in the first place, and a lot of those problems would be solved in the first place. But one can also hope that having the motivation to get agents running on those things could actually bring a lot of accessibility features to newer apps.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#3

Post by qsort » Tue, Dec 16, 2025, 10:22 AM UTC

This is very interesting if used judiciously, I can see many use cases where I'd want interfaces to be drawn dynamically (e.g. charts for business intelligence.)

What scares me is that even without arbitrary code generation, there's the potential for hallucinations and prompt injection to hit hard if a solution like this isn't sandboxed properly. An automatically generated "confirm purchase" button like in the shown example is... probably something I'd not make entirely unsupervised just yet.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#4

Post by jy14898 » Tue, Dec 16, 2025, 10:23 AM UTC

I never want to unknowingly use an app that's driven this way.

However, I'm happy it's happening because you don't need an LLM to use the protocol.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#5

Post by mbossie » Tue, Dec 16, 2025, 10:40 AM UTC

So there's MCP-UI, OpenAI's ChatKit widgets and now Google's A2UI, that I know of. And probably some more...

How many more variants are we introducing to solve the same problem. Sounds like a lot of wasted manhours to me.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#6

Post by raybb » Tue, Dec 16, 2025, 10:45 AM UTC

Is there a standard protocol for the way things like Cline sometimes give you multiple choice buttons to click on? Or how does that compare to something like this?

Re: A2UI: A Protocol for Agent-Driven Interfaces

#7

Post by [deleted] » Tue, Dec 16, 2025, 10:49 AM UTC

mbossie wrote: post #5

So there's MCP-UI, OpenAI's ChatKit widgets and now Google's A2UI, that I know of. And probably some more... How many more variants are we introducing to solve the same problem. Sounds like a lot of wasted manhours to me.

[deleted]

Re: A2UI: A Protocol for Agent-Driven Interfaces

#8

Post by MrOrelliOReilly » Tue, Dec 16, 2025, 10:53 AM UTC

mbossie wrote: post #5

So there's MCP-UI, OpenAI's ChatKit widgets and now Google's A2UI, that I know of. And probably some more... How many more variants are we introducing to solve the same problem. Sounds like a lot of wasted manhours to me.

I agree that it's annoying to have competing standards, but when dealing with a lot of unknowns it's better to allow divergence and exploration. It's a worse use of time to quibble over the best way to do things when we have no meaningful data yet to justify any decision. Companies need freedom to experiment on the best approach for all these new AI use cases. We'll then learn what is great/terrible in each approach. Over time, we should expect and encourage consolidation around a single set of standards.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#9

Post by codethief » Tue, Dec 16, 2025, 11:04 AM UTC

> A2UI lets agents send declarative component descriptions that clients render using their own native widgets. It's like having agents speak a universal UI language.

(emphasis mine)

Sounds like agents are suddenly able to do what developers have failed at for decades: Writing platform-independent UIs. Maybe this works for simple use cases but beyond that I'm skeptical.

Re: A2UI: A Protocol for Agent-Driven Interfaces

#10

Post by evalstate » Tue, Dec 16, 2025, 11:05 AM UTC

I quite like the look of this one - seems to fit somewhere between the rigid structure of MCP Elicitations and the freeform nature of MCP-UI/Skybridge.