agent-infrastructureHuman-reviewed editorial
A2A 0.2.5 requires protocol versions and supports multiple push configurations
A2A 0.2.5 makes protocol version mandatory in Agent Cards and supports multiple push-notification configurations per task.
Human read
Why this signal matters
Version 0.2.5 introduces two breaking contract changes with practical interoperability impact. Agent Cards must declare a protocol version, making negotiation explicit, and tasks can carry multiple push-notification configurations. Client, server, and persistence schemas need to migrate together, especially where code previously assumed one callback destination per task.
Agent parse
Actionable summary
For A2A 0.2.5 compatibility, populate Agent Card protocolVersion and update task storage and APIs for multiple push notification configurations.
- Agent usefulness
- 89/100
- Confidence
- 93%
- Canonical data
- JSON + Markdown
Classification
Tags and routing
a2aagent-cardpush-notificationsbreaking-change
Related signals