A2A, the agent-to-agent protocol Google launched in 2025, is now a formally hosted project at the Agentic AI Foundation. The announcement puts it alongside MCP, AGENTS.md, and Agentgateway under one governance roof. AAIF’s CTO, Manik Surtani, called it “an important step toward an open, interoperable future for AI agents.” Google Cloud’s Rao Surapaneni put the practical case more simply: A2A “enables agents to easily discover, delegate, and collaborate across frameworks.” More than 150 organizations back the standard now, with traffic already running through it at Huawei, Tencent’s WeChat, PayPal, and Google Cloud.
Our take on this is a good one. We’ve written before about wanting AAIF’s membership structure to work differently, and nothing here changes that view. But we don’t sit on AAIF’s board, we don’t have visibility into how these calls get made inside the foundation, and we’re not going to pretend otherwise by declaring what this does or doesn’t change institutionally. What we do have is a few months spent building directly on A2A, before any foundation had its name attached to it, and a clear sense of where we want to take that next. That’s what the rest of this post covers.
What we’ve already built on A2A
SuperQode’s A2A surface already lets external systems such as YC’s QM call SuperQode harnesses as peers: reading an Agent Card, submitting a task, and getting a structured result back, without absorbing SuperQode’s internals or forcing a shared runtime. SuperOptiX ships its own A2A v1 integration to expose, connect, and orchestrate agents across frameworks. The Harness Hub we introduced last week catalogs 97 harnesses and agents, most of them reachable over the Agent Client Protocol, a different specification from the Agent Communication Protocol that folded into A2A last year, easy to mix up since both get shortened to ACP. None of this was built because a foundation told us to. It was built because teams kept asking how to call one coding harness from another without rewriting the integration each time, and A2A was the cleanest answer on offer, a case we made in more detail in an earlier post.
That work is not limited to our own products. Through Agent Experience, we build A2A protocol surfaces from the ground up for any agent framework and any stack, so a team on Google ADK, Gemini Enterprise, Microsoft Foundry, or Agentforce can be reached the same way a team on SuperQode can. SuperOptiX already carries native support for eight agent frameworks, DSPy, OpenAI, Claude SDK, Google ADK, Pydantic AI, CrewAI, DeepAgents, and Microsoft, so most teams are not starting that integration from zero.
What we want to build next
SuperQode’s A2A surface already has a defined structure: an Agent Card served at a well-known location that advertises identity, skills, and interface endpoints, and tasks that carry a lifecycle state from submission through to a completed result. What we want next is that surface available wherever SuperQode runs, not just from one entry point, so a coding agent can reach another coding agent no matter which platform started the session.
Alongside that, we are hardening SuperOptiX’s A2A support across every agent framework it already runs, DSPy, OpenAI, Claude SDK, Google ADK, Pydantic AI, CrewAI, DeepAgents, and Microsoft, so A2A behaves the same way regardless of which framework built the agent on the other end. Between the two, SuperQode and SuperOptiX are heading toward stronger A2A support than either has had before.
An open invitation
SuperQode has led coding-harness adoption of A2A from the start, and we want that lead to turn into more builders talking to each other, not just a longer feature list. If you are building on A2A, on any agent framework or runtime, running a coding harness over it, or sitting in one of AAIF’s working groups, we would like to compare notes. We are not asking for a seat that costs $350,000 to sit in. We are asking whether the people running this protocol day to day want to talk to each other about what it still needs. If your stack sits on a different framework entirely, our Agent Experience work and SuperOptiX’s framework support exist for exactly that case. SuperQode is open source, the A2A surface and the Harness Hub catalog are both public, and reaching us is one message away. That is the part of this news we can act on, and it is where we plan to spend our time.