I work on agents that can work with each other, and with us. A2A for agent collaboration. A2UI for agents driving your design system. Open standards with AAIF. I'll share things I'm building, questions I'm stuck on, and what we learn making these work outside demos.
a much anticipated launch! amazing seeing the work @CopilotKit and @Google co-contributed to A2UI go live
🤸♂️play around with it at https://t.co/D4ts8iSwDM
big thanks to @zeroasterisk & @MotwaniVishal for enabling this partnership
@LaithAljunaidy@GoogleCloudTech Answer: the protocol is agnostic. Streams come in and variables are hydrated, renderers would render RTL.
I imagine some layout examples (skills) you may give differently for RTL, but I'm assured it should just work.
Let me know
@jessicayxw@GoogleCloudTech A2UI is a type of message + sytems to handle it.
It can be emitted by a tool, a workflow, a system one model making choices or (often) by a LLM. The LLM choses to emit A2UI based on instructions, examples, skills, etc... or a fine-tuned model can specialize
@gaurav0bhowmick@GoogleCloudTech Love the question. Components are drawn on the screen. Those components must have accessibility. A2UI can help with filling in variables, and adhering to design choices (catalog or skill)... but ultimately, it's up to the front end to have affordances
@jacksunwei@GoogleCloudTech Indeed. https://t.co/10a8J4rgmq
3 flavors of MCP Apps + A2UI all official.
Another PR draft from @liadyosef where A2UI renderers could be native widget for MCP Apps without any change to MCP Apps aside from mediaType
@progerallworld@GoogleCloudTech The promise is - that the front end catalog is a contract... so the back end agent should only get the components in the current catalog. Failover should always be plain text but you can build prettier handlers if you want
@jul1anodev@GoogleCloudTech You're in charge of _how_ it works... demos make some design choices, but you can store whatever you want, across refreshes, sessions, etc... it's just message passing
@notinvariant@GoogleCloudTech There are a few data contract changes, but the SDKs and dev tooling should make it pretty much drop in. If you support multiple versions it gets slightly more complex, but again, the SDKs should help coordinate versions
@karpathy I've tried "Create a 3b1b style video explainer" for many months and so far it's been pretty terrible, even with skills... I tried to make a grader for "good video" but failed. Do you have a recipe?
@addyosmani You are speaking to my heart here.
You know my background with A/B experimentation, smart routing w/ redundancies, and heroic regression testing as mechanisms to gain confidence, because we don't trust the world... same stuff applies to "untrusted rapidly changing codebases"