Conventions and/or protocol for visualisation in a UI

[ydennisy]

Hey All!

I am interested to hear what ideas or conventions are appearing around the UI of an A2A client.

I feel we are all going to be implementing similar ideas such as for example:

• rendering of tool calls
• rendering of forms

We have an attempt to create a protocol in this space: https://docs.ag-ui.com/introduction - do people plan to use AGUI for this purpose? Are there interesting alternatives?

Looking forward to your thoughts!

[benclarkegithub]

Hey Dennis!

I think A2A changes the game to some degree, because A2A is a communication layer for agents. For me, it's not clear that there will always be a clear separation between an "agent that communicates with people" and an "agent that communicates with agents".

As far as I'm aware there is currently no standard for visualising tool calls, forms, etc. There is an A2A sample where forms are sent as a DataPart Message with type="form" and a form object (see the ADK Expense Reimbursement Agent).

It would be great to converge on something, ideally reusing well-known, pre-existing standards. I've implemented an Agent2Agent (A2A) UI and talk a little bit more about the subject here The Agent2Agent (A2A) Protocol is HTTP for Agents.

[ydennisy]

Hey @benclarkegithub

Sorry about the late reply and thank you for your message.

I had actually seen your project and have followed some of the patterns you used :)

I feel its very important we converge on something so we do not have to keep re-implementing boring UI tidbits!

have you seen AGUI, do you have thoughts on how it would or would not work with A2A?

[benclarkegithub]

No worries. I have read through the AG-UI documentation but wouldn't call myself an expert. Have you thought about supporting A2A as if it were a framework? Then any A2A compatible agent would work with AG-UI.