Google has published a new A2A update that shifts the Agent2Agent protocol from abstract interoperability talk toward a concrete multi-agent workflow.

The post marks one year since Google introduced A2A and frames the protocol as a way for agents to collaborate without being reduced to stateless tools behind a rigid API. The public A2A repository describes the protocol more narrowly as an open interface for communication and interoperability between opaque agentic applications, which is the useful baseline: agents can expose capabilities and exchange work without sharing their entire internal implementation.

Google's example is FoldRun, a life-sciences workflow in the Google Cloud Platform LifeSciences repository. The blog presents it as an agentic interface for protein-structure prediction, where a developer can pull a FoldRun image, register the agent in an A2A-supported environment, and delegate the specialized scientific workflow instead of rebuilding the full infrastructure stack inside a general assistant.

That makes the update more relevant to developers than a simple protocol anniversary. A2A's practical promise is cleaner separation between a coordinating agent and domain agents that own their own context, credentials, tools, and workflows. In a production setting, that could reduce context pollution and make handoffs easier to audit, but it also creates new questions about trust boundaries, capability discovery, and failure handling across independently operated agents.

The conservative read is that A2A is still early infrastructure. FoldRun gives the protocol a more tangible reference point, while the hard work remains in making cross-agent handoffs reliable enough for teams outside tightly controlled demos.