The context · April 2025
Google introduced the Agent2Agent protocol in April 2025 to support communication and collaboration between agents built with different tools and frameworks. [1]
A connection is not a working agreement
Two systems may be able to exchange a task without agreeing on what successful completion means. One may call a draft finished while the other expects a verified result. In a business process, those differences become missed work, duplicate effort or an action nobody intended to authorise.
Design the receipt
Every handover should identify the requested outcome, the information supplied and the limits on what the receiving system may do. A useful response includes the result, its status and any unresolved questions. A timeout should lead to a visible exception rather than a silent retry loop.
Give the workflow an owner
Cross-system work needs someone accountable for the complete process. That owner should be able to inspect the chain, stop it and resolve an exception. Standardised communication is valuable plumbing; the business value comes from a process people can understand and operate.
Source & context
Google Developers · Agent2Agent, 9 April 2025This retrospective was written for the archive in September 2026. The linked primary source documents the announcement or event; the practical interpretation and proposed approach are Sansa’s editorial perspective. Public examples do not imply a client relationship. Product capabilities and guidance may have changed since the period discussed.
Another perspective · April 2025
A read-only handover between two assistants
Continue readingWorking through a similar question?
Talk it through with Sansa