Published

Google ADK 2.14.0 stabilizes A2A and environments, adds repeated parallel evaluation and Teams integration

Google’s Python Agent Development Kit release 2.14.0 on GitHub moves a set of environment, A2A, evaluation and core runtime interfaces out of experimental status. It adds concurrent repeated evaluation, semantic tool-argument comparison and Microsoft Teams integration, alongside API and storage changes that matter when upgrading.

The changes mainly concern developers already building and deploying agents. The official notes mark BaseEnvironment, LocalEnvironment, DaytonaEnvironment, E2BEnvironment and related environment interfaces, along with A2A integration, as stable. Groups of auth, environment, app, CLI and cache modules and toolset features also lose experimental labels. This concerns those specific interfaces, not a promise that every ADK feature is now fixed.

Evaluation gains MultiRunConfig and CLI controls for repeated runs and parallelism. Each test case can run concurrently multiple times before scores or pass rates are combined. ToolArgsMatcher supports exact, case-insensitive, numeric-tolerance and language-model-assisted semantic checks of tool arguments in evaluations and environment simulation. It does not mean every check now uses a model judge.

For integrations, TeamsRunner connects an ADK agent to Microsoft Teams chats and channels. OpenAIDecisionsClassifier uses the Decisions API for workflow and tool-gating questions. MongoDbMemoryService adds vector retrieval and memory-expiration configuration. These are toolchain integrations, not a new general-purpose model release.

Several breaking changes need migration checks. FunctionTool enum arguments now arrive as enum members rather than raw strings, which can affect string comparisons and serialization. RunSkillScriptTool in environment mode no longer accepts a free-form command and instead uses validated script arguments. VertexAiSessionService.create_session also narrows the accepted session-configuration fields.

Storage and rollback have conditions too. The notes say FirestoreSessionService stores event payloads as JSON strings and wraps nested lists in state; sessions written by this version cannot be read directly by the earlier version, so rollback compatibility needs checking. The release also reports speed and memory improvements on a particular long workflow. Those are maintainer-reported results for that case, not guarantees for every deployment.

The GitHub release was published at 08:58:18 on November 7 in Shanghai time; the version heading inside its notes separately says November 4. This report is archived by the public release timestamp, not by treating those two labels as interchangeable. Teams planning an upgrade should first validate existing tool arguments, script calls and session rollback paths.

Sources

  1. v2.14.0 — Google / google/adk-python

Topics:Google

Related stories

Open this story in Shift →