Google has shipped Agent Development Kit 2.14.0, the release that moves its agent-to-agent communication protocol out of experimental status and into stable. The Python package, known as google-adk, was released on 7 November 2026.

The release graduates execution environments, the agent-to-agent (A2A) protocol, evaluation tools and core runtime modules from experimental to stable, according to the release notes on GitHub. In total, 26 modules covering authentication, environments, apps, the command line and caching move to stable, alongside 16 toolset integrations.

A2A is the protocol that lets AI agents built by different teams, and running on different systems, talk to each other and hand work back and forth. Making it stable matters because developers can now build multi-agent systems on it with a dependable API surface, rather than one that may change in the next release. The release also adds an adk generate_agent_card command that builds A2A agent cards from the command line, describing what an agent can do so other agents can find and use it.

The execution environments going stable cover the places agents actually run. Local environments sit alongside sandboxed cloud options from Daytona and E2B, so the same agent code can move from a developer’s laptop to a hosted run without changing how it executes. Evaluation classes graduating at the same time means the testing tools developers use to check an agent’s behaviour are now on the same stable footing as the runtime itself.

The release also wires ADK agents into Microsoft Teams. A new TeamsRunner connects an agent to Teams, so the same agent that runs in a developer’s test setup can answer and act inside the chat tool many workplaces already use. Evaluation gets multi-run support, letting developers test an agent across repeated runs instead of a single pass, and a new MongoDbMemoryService adds vector-search retrieval and expiry dates for agent memory.

Google claims a 30-node workflow running 200 turns is 23 percent faster with 9 percent lower peak memory in this release. That is Google’s own claim: the release notes publish no baseline hardware, no comparison against a named earlier version and no second benchmark, so developers should treat it as a direction of travel rather than a guarantee for their own workloads.

Stable status is a maturity milestone, not a promise that any particular application is ready for production. Security, reliability and testing of the finished application still sit with the team shipping it. But for developers who have been waiting for Google’s agent framework to settle before committing to it, ADK 2.14.0 is the release that says the core pieces are no longer experiments.