A2A Joins AAIF: The 2026 Agent Protocol Consolidation

The Agent2Agent (A2A) protocol is joining the Agentic AI Foundation as a hosted project, announced on August 17, 2026. The move takes A2A out of the Linux Foundation's broader portfolio and into its agent-specific foundation, alongside MCP, goose, AGENTS.md, and agentgateway.¹²

TL;DR

A2A defines how independent AI agents discover each other, delegate tasks, and exchange results across framework and vendor boundaries. MCP defines how a single agent reaches tools and data.

Until the August 17 announcement, those two layers lived under different governance structures inside the Linux Foundation. Now they share one.

For teams shipping multi-agent systems, this is a supply-chain change rather than a technical one. No spec version bumped. No API broke. What changed is who decides what happens next.

What You'll Learn

• What the August 17 transfer actually moved, and what it did not
• How AAIF's five stack layers divide agent responsibilities between them
• Where A2A is already running in production, including at mobile-OS scale
• One contributor-concentration number that complicates the neutrality story
• What the consolidation changes for teams already building on A2A or MCP

What actually changed on August 17

A2A moved from being a standalone Linux Foundation project to being a hosted project inside the Agentic AI Foundation (AAIF), which the Linux Foundation announced on December 9, 2025 and continues to host.¹³

That is a governance move, not a technical one. AAIF's announcement points readers to the same specification site, the same SDKs, the same Discord, and the same A2A Technical Steering Committee calendar as before.¹

What changes is the layer above that. A2A's own TSC keeps running the protocol; the foundation-level bodies it now sits beneath are AAIF's governing board and Technical Committee — the same ones above MCP, chaired respectively by AWS's David Nalley and Anthropic's David Soria Parra.⁴

AAIF framed the reasoning in stack terms rather than political ones. "It also means the full stack, from context to communication to operations to the open agent layer, is governed in the same way and in the same place," the foundation wrote in its announcement.¹

Axios reported the move the same day as an exclusive, noting AAIF has grown to more than 250 members since launch.²

Both the growth and the baseline are worth pinning down. The 250+ figure is AAIF's own; Axios puts the starting point at "fewer than 40 members" eight months earlier.² Counting every company the Linux Foundation actually named across the Platinum, Gold, and Silver tiers in its December 2025 launch release gives 49.³ Either way the foundation has grown five- to six-fold since launch.

AAIF's five layers, and where A2A sits

The foundation's announcement laid out its projects as distinct layers of a single stack.

A2A is the most recent project to land under AAIF. Three arrived at launch — Anthropic's MCP, Block's goose, and OpenAI's AGENTS.md.³ agentgateway, an Apache 2.0 gateway for MCP, A2A, LLM inference, and API traffic, joined on June 4, 2026 as the fourth.⁵

The layer boundaries matter more than the count. MCP and A2A are frequently described as competitors; the Linux Foundation's framing is that they are complementary, with A2A defining how agents coordinate across organizational boundaries and MCP defining how an agent reaches internal tools and data.⁶

MCP has kept moving independently through all of this — its stateless 2026-07-28 specification published three weeks before A2A joined it under AAIF, with the Enterprise-Managed Authorization extension having gone stable that June.

How A2A got here

The protocol has changed governance homes twice in the seventeen months since its first commit.

The IBM merger is the underrated entry in that list. The ACP team wound down active development and began contributing its technology and expertise directly to A2A, with a migration guide for existing ACP users.⁹

IBM Research's Kate Blair, who had overseen ACP's development, joined the A2A Technical Steering Committee alongside representatives from Google, Microsoft, AWS, Cisco, Salesforce, ServiceNow, and SAP.⁹

A competing protocol folding in rather than persisting alongside was an early signal that the industry would converge on one inter-agent standard instead of several.¹

A2A v1.0 in March 2026 added multi-protocol bindings, version negotiation, enterprise multi-tenancy, and signed agent cards for cryptographic identity verification.¹⁶ Those are the features that make a protocol deployable rather than demonstrable.

If you have not worked with the spec directly, our A2A protocol Python tutorial covers what changed in v1.0 and walks through defining an Agent Skill and Agent Card, then calling the agent.

Where A2A is already running

The AAIF announcement named production deployments that go well beyond enterprise pilots.

Huawei has standardized A2A as the protocol between Celia, its OS-level assistant, and in-app agents across the HarmonyOS developer platform.¹ Supported flows include Celia handing a long-running task to an app agent, controlling app UI through an agent, and requesting contextual recommendations from one.

Tencent's WeChat is among the first major apps integrating with Huawei and other Android OEM assistants over A2A, covering messages, voice calls, and video calls initiated through an assistant, with dual authorization through the protocol.¹

That is agent-to-agent communication running at mobile-platform scale, which is a materially different reliability bar than an internal enterprise workflow.

On the cloud side, Google Cloud, Microsoft, and AWS all support A2A natively. Google Cloud supports building and deploying A2A agents through ADK, Agent Engine, Cloud Run, and GKE. Microsoft Foundry lets agents expose A2A endpoints and discover external agents — AAIF's post still calls it by its former name, Azure AI Foundry, which Microsoft renamed at Ignite in November 2025. AWS Bedrock AgentCore can host and operate A2A servers.¹¹⁰

Google Cloud and PayPal are also extending A2A into agentic commerce via the Agent Payments Protocol (AP2), which the Linux Foundation reported had support from more than 60 organizations across payments and financial services as of April 2026.¹⁶

The number that complicates the neutrality story

Here is the tension worth naming, and it comes from the Linux Foundation's own dashboard.

AAIF's case for hosting A2A rests on breadth: 150+ supporting organizations, many of them direct competitors, held together by governance no single participant controls.¹

But LFX Insights shows that for the 365 days ending August 25, 2026, three organizations account for 51% or more of A2A's recorded contributions, and five individual contributors do too.⁷ LFX counts a contribution as commits, issues, or pull requests — not code alone. It labels the project's organizational diversity "modest" and the spread across individuals "moderate."

Supporting a protocol and writing it are different activities. Neutral governance changes who sets the charter and who arbitrates roadmap disputes; it does not, on its own, redistribute who writes the code.

The rest of the picture is strong, and LFX rates A2A's overall health score "Excellent." The dashboard reports 89 active contributors in the last quarter, 29% quarter-over-quarter retention, roughly 363 new pull requests per month, and activity on all 365 of the last 365 days.⁷ Average issue resolution runs 56 days, which LFX flags as slow.

None of that argues against the move. It argues for reading "vendor-neutral" as a statement about governance structure rather than about contributor distribution — a distinction that matters if your production system depends on the protocol's roadmap.

What this changes for teams building agents

For most engineering teams, the honest answer is: not much this quarter, and something real over the next few years.

Nothing breaks. No spec version changed. The A2A specification site still lists 1.0.0 as the latest released version as of August 25, 2026.¹¹ Existing agent cards, SDKs, and endpoints keep working.

Roadmap risk drops slightly. A protocol governed by a foundation charter is less exposed to a single vendor's product decisions than one governed by a single vendor. That is the concrete benefit AAIF is selling, and it is real if modest.

Cross-layer coordination gets easier. MCP and A2A overlap at the edges — identity, authorization, observability. Two projects under one technical committee should be able to resolve those seams faster than two projects under separate ones — though that is an expectation, not something the move guarantees.

Procurement gets a cleaner story. For teams that had to justify a protocol dependency to a risk or architecture review, "Linux Foundation project under a multi-vendor foundation" is an easier sentence than "Google-created standard."

What it does not do is settle the standards question. A foundation charter is not an IETF RFC, and the agentproto BoF at IETF 126 put both MCP and A2A under a different kind of scrutiny entirely. Foundation governance and standards-body ratification are parallel tracks, not the same one.

The bottom line

The agent protocol layer has consolidated fast. Seventeen months after A2A's first commit, the two protocols that define how agents talk to tools and to each other are governed by the same foundation — one whose Platinum members include AWS, Google, Microsoft, Anthropic, and OpenAI.⁴

The caveat is the one the dashboard supplies. Governance neutrality and contribution neutrality are separate properties, and A2A currently has more of the first than the second. Three organizations still account for most of the recorded contribution activity.

If you are building on A2A, the practical move is unchanged: pin your SDK versions, treat agent card discovery as an untrusted input, and follow the TSC calendar rather than the press releases. The foundation move makes the roadmap more predictable. It does not make it someone else's problem.

References