A new proposal asks the fundamental question: as A2A matures past 1.0, how should the community manage extensions without fragmenting the ecosystem? The answer will shape agent interoperability for years to come.
A2A 1.0 is intentionally minimal. It defines the core primitives for agent-to-agent communication: tasks, messages, artifacts, and the machinery to coordinate them. But real-world deployments need more:
Without governance, extensions proliferate incompatibly. Two agents might both "support" progress reporting—but use different schemas, making them unable to interoperate. This is the classic extensibility trap that has fragmented protocols before.
While the full framework is still being discussed, the issue raises several governance mechanisms worth considering:
A central (or federated) registry where extensions are documented, versioned, and discoverable. Agents could query the registry to understand each other's capabilities.
Standardized mechanisms for agents to advertise which extensions they support and negotiate common ground at connection time.
Similar to W3C's Recommendation track or IETF's RFC process:
The W3C's extensible web movement and IETF's RFC process offer models, but agent protocols have unique challenges: agents must negotiate capabilities in real-time, often without human intervention. The governance framework must account for autonomous capability discovery.
This proposal surfaces a fundamental tension:
Move fast: Let anyone publish extensions. Innovation happens at the edges. The best extensions will win through adoption.
Maintain coherence: Curate extensions carefully. Require compatibility testing. Prevent fragmentation that undermines the protocol's value.
A2A must find the balance. Too much control stifles innovation; too little creates the fragmented mess that XMPP extensions became.
The proposal to remove extensions from Message and Artifact (also opened this week) is directly related. If base primitives can't carry extensions, where do they go? The governance framework must address this.
Today: The 1.0 spec is stable. Extensions are ad-hoc. If you need capabilities beyond the base spec, expect to handle compatibility yourself.
Soon: Watch this governance discussion. If you're building extensions, participate. Early input shapes the framework.
Eventually: A governance framework will likely emerge. Position your extensions to align with whatever maturity model is adopted.
A2A's governance decisions will influence the entire agentic ecosystem:
Getting governance right isn't just about A2A—it's about establishing patterns for how autonomous agent protocols evolve industry-wide.