Google's Agent-to-Agent Protocol approaches its 1.0 milestone with a flurry of spec refinements — clarifying timestamps, simplifying IDs, and enabling SDK backwards compatibility.
The A2A project is in the final stretch before 1.0, and this week saw an intense focus on spec consistency. A single contributor (yarolegovich) filed four issues in one day identifying inconsistencies in the release candidate — exactly the kind of careful review a protocol needs before locking in a stable version.
This isn't just cleanup. These changes affect how every A2A SDK will be built and how agents will communicate for years to come.
Task and message IDs are changing from complex objects to simple strings. This reduces JSON payload size, simplifies parsing, and aligns with how most developers actually use IDs. Breaking change, but worth it before 1.0. View PR →
New spec fields enable SDKs to gracefully handle version differences. This means an A2A 1.0 agent can still communicate with a 0.3 agent — critical for real-world adoption where not everyone upgrades simultaneously. View PR →
ISO 8601 timestamps in query parameters now have explicit encoding rules. Sounds minor, but ambiguous timestamp parsing has caused countless production bugs. Getting this right in the spec prevents a class of interoperability issues. View PR →
The spec now clearly distinguishes between messages (conversational) and artifacts (output data). This semantic clarity helps developers choose the right abstraction for their use case. View PR →
Several issues filed this week highlight ongoing design tensions:
The GOVERNANCE.md update this week formalizes the project's structure. A2A now has clear processes for:
This institutionalization signals Google's commitment to A2A as a long-term, multi-vendor standard — not just a Google project.
Protocol 1.0 releases are like constitutional moments — they establish precedents that persist for years. The A2A team is wisely using this final window to:
For SDK developers: Now is the time to audit your A2A implementation against the 1.0-rc spec. Breaking changes are still possible, but the window is closing. File issues for any inconsistencies you find — the team is clearly responsive.
Based on the current pace and the governance formalization, expect A2A 1.0 stable within 4-6 weeks. The project appears to be in "hardening" mode — no new features, just spec refinement and documentation.