A2A Protocol v1.0: Agent Communication, Explained

On April 9, 2026, the Agent-to-Agent Protocol (A2A) v1.0 specification was released under Linux Foundation governance (Linux Foundation, 2026). Originally initiated by Google, A2A defines how AI agents from different vendors, runtime environments, and organizations communicate with each other in production. The v1.0 milestone marks the transition from vendor-controlled specification to industry-governed standard, with 150+ member organizations and confirmed production implementations from Microsoft, Amazon Web Services, and Google.

What v1.0 specifies

A2A defines a communication layer for agent interoperability. The v1.0 specification covers four functional areas:

Signed Agent Cardsa structured identity and capability declaration for each agent, cryptographically signed to enable trust verification across organizational boundaries (A2A Protocol, 2026). An agent presenting a Signed Agent Card can be authenticated without a pre-existing integration agreement between the organizations involved.

Task protocola standardized message format for initiating, tracking, and terminating tasks between agents, with defined state machine semantics for task lifecycle management.

Streaming supportreal-time event streaming for long-running tasks, enabling agents to report intermediate states rather than waiting for task completion before returning results.

Multi-SDK coverageofficial SDKs in Python, JavaScript, Java, Go, and .NET are part of the v1.0 release. This is the coverage required for enterprise polyglot environments, not a research-grade release.

Linux Foundation governance: what changes

The transfer from Google-initiated specification to Linux Foundation governance changes the political economy of A2A adoption. Linux Foundation projects operate under an open governance model, specification changes require consensus from the member organizations, and no single vendor controls the roadmap. For enterprise technology procurement, this matters: A2A becomes a standard to adopt rather than a Google product to evaluate.

The 150+ member organizations include cloud providers, enterprise software vendors, and system integrators. Microsoft, AWS, and Google in production means A2A is now a table-stakes requirement for any enterprise agent deployment that touches cross-vendor infrastructure.

The architectural decision this creates

Any organization building multi-agent systems faces a concrete decision: build proprietary agent communication on top of LLM APIs, or adopt A2A as the communication layer and focus engineering investment on agent capability rather than agent plumbing.

The trade-off is real. A2A adoption creates dependency on an evolving specification maintained by committee, specification changes will require SDK updates and potential compatibility testing. Proprietary communication avoids that dependency and allows faster iteration on internal requirements.

The v1.0 stability signal changes this calculation. A v1.0 release under Linux Foundation governance with production deployments from three major cloud providers is a different technical maturity signal than a v0.x specification from a single vendor. The risk profile of adopting A2A now is measurably lower than it was at launch.

What to assess in your current agent stack

CTO and Head of Engineering decisions for the next planning cycle: map which of your current or planned agent integrations cross organizational or cloud-provider boundaries. For each boundary crossing, assess whether A2A adoption reduces complexity relative to bespoke integration. Evaluate your SDK language coverage against the five official A2A SDKs. And review your identity and trust model for agent-to-agent interactions, Signed Agent Cards resolve the authentication problem that has been handled inconsistently in earlier agent deployments.

→ The propagation dynamics of failures in multi-agent architectures, and why communication layer design matters for reliability: Hallucination Cascade in Multi-Agent Systems.

This deskAutomation & Processes | Source: A2A Protocol v1.0 specification, Linux Foundation, April 9, 2026. GitHub: google/A2A. Working group roster: Linux Foundation project page.