Google's Agent-to-Agent Protocol reaches its 1.0 milestone with a comprehensive migration guide. For the growing ecosystem of A2A implementers, this documentation clarifies the path from experimental adoption to production deployment.
Protocol specifications often ship breaking changes without clear migration paths. The result: fragmented implementations, frustrated developers, and ecosystem fragmentation. By documenting the v0.3.0 → v1.0 changes explicitly, the A2A team is investing in implementer success.
This documentation also serves as a historical record. As the protocol continues to evolve post-1.0, understanding why certain decisions were made becomes increasingly valuable.
The most significant breaking change: A2A 1.0 switches to non-complex IDs in requests (PR #1389). Previously, request identifiers could be structured objects. Now they're simple strings.
If your implementation relied on structured ID metadata, you'll need to move that information elsewhere. The simplification improves interoperability but may require refactoring ID generation logic.
How do you pass timestamps in URLs? PR #1425 adds explicit guidance on encoding timestamps in HTTP query parameters, eliminating ambiguity around timezone handling and format.
The relationship between messages and artifacts has been clarified (PR #1424). This addresses common confusion about when to use each construct and how they relate.
Merged today (#1458), the streaming examples now accurately reflect the 1.0 wire format. Documentation drift is a common problem in fast-moving specs; these fixes ensure new implementers start with correct patterns.
For existing v0.3.0 implementations: Review the migration guide carefully. The ID simplification is the most likely breaking change, but timestamp handling may also affect your HTTP client code.
For new implementations: Start with 1.0. The spec is now stable enough for production use, and the documentation quality signals maintainer commitment to the ecosystem.
For protocol designers: A2A's approach to migration documentation is worth studying. Explicit change tracking, linked PRs, and clear migration guidance reduce the burden on implementers.
A2A 1.0 arrives at a critical moment for agent interoperability. With Agent-Mesh Trust Layer proposals emerging and enterprise adoption accelerating, the protocol needs stability. This documentation signals that stability.
Combined with the ongoing UCP request signing work, we're seeing the agentic commerce stack mature from experimental to production-grade. The next year will test whether these protocols can handle real-world agent coordination at scale.