Where A2A Fits in the Open Agent Ecosystem Co-authored with Angie Jones on the Agentic AI Foundation blog, August 20, 2026
A2A defines how one independent agent works with another: negotiating scope, keeping a task going over time, asking for more input, and streaming intermediate updates, while the remote agent decides how to do the work behind its endpoint. Commerce is a concrete example. UCP defines an A2A binding for checkout, and AP2 carries verifiable payment authorization inside the same interaction.
How A2A is Building a World of Collaborative Agents Originally published on Google Developers Blog - June 18, 2026, co-authored with Frank Guan and Nick Losier.
The Agent-to-Agent (A2A) protocol is shifting AI development away from isolated, single-purpose tools toward a collaborative ecosystem — enabling secure, autonomous handoffs between agents and scalable workflows like FoldRun.
Why This Matters A2A is the connective tissue that lets agents built by different teams, on different stacks, actually work together safely.
Building Agents with the ADK and the New Interactions API Originally published on Google Developers Blog - December 11, 2025, co-authored with Mike Smith and Xiang (Sean) Zhou.
The landscape of AI development is shifting from stateless request-response cycles to stateful, multi-turn agentic interactions. The new Interactions API lets you power ADK agents or connect A2A systems directly to the Gemini Deep Research Agent.
Why This Matters Stateful, multi-turn interaction patterns are exactly where agent memory systems earn their keep — this API gives ADK and A2A a standard way to plug into long-running, stateful agent experiences.