Roadmap

Last updated: September 15, 2026

Near-term initiatives

v1.1 protocol enhancements and core robustness (#1991 ): Advance v1.1 features by refining the task timeline specification, standardizing event filtering mechanisms for backward compatibility, and establishing clear guidelines for how agents handle messages received while working.
Bidirectional (BiDi) streaming (#1995 ): Introduce robust streaming capabilities that support real-time artifact updates, role management, and continuous multi-turn messaging while agents are actively executing tasks.
A2A CLI and coding harness integration (#1929 ): Deliver the new A2A CLI to bridge the adoption gap in coding harness tools. The CLI’s client interface makes exchanging messages between agents and A2A instances straightforward. See Introducing the A2A CLI .
Elicitation and multi-turn workflows (#2149 , #2143 ): Explore structured human-in-the-loop interaction models and multi-round negotiation patterns informed by telecom industry use cases, to support complex multi-turn agent collaboration.

Longer term (3 to 6 months)

Governance

The Technical Steering Committee (TSC) aims to streamline opportunities for contribution through A2A extensions , samples , and community participation. The promotion process for extensions and custom bindings is described in Extension and Binding Governance .

Validation

As the A2A ecosystem matures, the community needs tools to validate agent implementations. Two efforts are under way: the A2A Inspector and the A2A Protocol Technology Compatibility Kit (TCK).

SDKs

The A2A project currently hosts SDKs in six languages: Python, Go, JavaScript, Java, .NET, and Rust. See Official SDKs .

Community best practices

As companies and individuals deploy A2A systems at an increasing pace, the community plans to accelerate learning by collecting and sharing the best practices and success stories that A2A has enabled.