# Google’s ADK launch put multi-agent composition beside precise behavior control Google introduced Agent Development Kit at Cloud Next on April 9, 2025 as an open-source framework for building agents and multi-agent systems. Canonical: https://rangoon.ai/insights/archive-google-adk-april-2025/ Author: Rangoon Editorial (https://rangoon.ai/insights/editorial/) Published: 2026-10-23 Updated: 2026-10-23 Event date: 2025-04-09 Tags: [Google](https://rangoon.ai/insights/tags/google/), [ADK](https://rangoon.ai/insights/tags/adk/), [Agent Development Kit](https://rangoon.ai/insights/tags/agent-development-kit/), [multi-agent systems](https://rangoon.ai/insights/tags/multi-agent-systems/) Source note: Historical reporting: Google introduced ADK at Cloud Next on April 9, 2025. The sources describe launch scope and supplier intent, not a current deployment guarantee. Image: Agent behavior layers. Original Rangoon explanatory diagram: concepts for editorial review, not measured results, an official legal determination, vendor interface or event photograph. ## Key takeaways - ADK was announced as an open-source multi-agent framework. - Behavior control must be tested at model, tool and workflow layers. - A low-code sample is not operational evidence for a production agent. ## Cloud Next made ADK part of Google’s agent-building stack [source 1](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai?hl=en) [source 2](https://blog.google/company-news/inside-google/message-ceo/alphabet-earnings-q1-2025/) Google’s Cloud Next 2025 announcement said it had unveiled Agent Development Kit, an open-source framework for building agents while maintaining control over agent behavior. The same release placed ADK beside Agent2Agent and Agent Garden. Google’s April 24 earnings-call remarks again described ADK as an open-source framework for sophisticated agents and multi-agent systems. These are first-party descriptions of an April launch, not a measured comparison with other frameworks or a claim that every behavior control is automatic. The dated Vertex AI post is more specific than the general Next recap. It names ADK, Agent Engine, A2A, MCP and Agent Garden as connected but distinct pieces of a multi-agent offering. That distinction matters because an open development framework, a managed runtime and a cross-agent protocol introduce different operational obligations. ## Framework composition does not collapse the layers of control [source 1](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai?hl=en) [source 2](https://blog.google/company-news/inside-google/message-ceo/alphabet-earnings-q1-2025/) A useful agent architecture separates model instructions, tool interfaces, workflow routing, memory or state, and deployment identity. ADK’s announced multi-agent framing makes those boundaries especially important: one component may decide, another may invoke an API, and a third may expose a result to a user. A code sample under one hundred lines can demonstrate composition, but it does not show authority limits, data classification, tool reliability or an adequate recovery path for a business process. Google described deterministic guardrails and orchestration controls alongside ADK. A review should ask where those controls execute and whether an untrusted tool response can bypass them. Model-facing instructions can inform a choice, but deterministic checks must validate arguments and routing after the choice is made. ## Agent behavior needs fixtures that include tool refusal [source 1](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai?hl=en) [source 2](https://blog.google/company-news/inside-google/message-ceo/alphabet-earnings-q1-2025/) Build a compact suite around the agent’s actual objective. Include normal requests, ambiguous requests, malformed tool arguments, an unavailable dependency, an overbroad request and a task requiring human approval. Record which agent saw which context and why a route was selected. If a tool changes data or calls an external service, put the policy enforcement outside the model’s natural-language instruction so an unexpected completion cannot decide its own privilege. Because the announcement described local debugging and containerized deployment targets, run the same fixture in both environments. Compare tool visibility, identity, timeouts and error handling. A local agent can appear correct while production changes network reachability, credentials, concurrency, or the available model catalogue. ## Analysis: compare framework paths with one task contract [source 1](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai?hl=en) [source 2](https://blog.google/company-news/inside-google/message-ceo/alphabet-earnings-q1-2025/) When comparing ADK or another framework, hold task, model, tool set and input corpus constant. Evaluate successful completion, unnecessary actions, error recovery, observability completeness and operator effort. Supplier framing around sophisticated systems is a reason to define the task carefully, not evidence that a particular deployment will be sophisticated or reliable. Use a versioned result table with both passes and stop conditions. A multi-agent comparison should count coordination cost explicitly: number of model turns, duplicate context, handoffs, tool calls and human interventions. These measures show whether a decomposition helps the stated workload. They also expose a common failure where specialized agents merely repeat each other because their boundaries were never made concrete. ## Sources 1. [Google Cloud Blog: Vertex AI multi-agent systems and ADK](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai?hl=en) 2. [Google Blog: Alphabet Q1 2025 earnings call remarks](https://blog.google/company-news/inside-google/message-ceo/alphabet-earnings-q1-2025/) ## Related reading - [Google’s Gemini Robotics On-Device put a vision-language-action model on the robot](https://rangoon.ai/insights/archive-google-gemini-robotics-on-device-june-2025/) - [Google put Guided Learning into Gemini with LearnLM-informed study tools](https://rangoon.ai/insights/archive-google-gemini-guided-learning-august-2025/) - [Google placed AI Mode in Search Labs as a query-fan-out experiment for complex questions](https://rangoon.ai/insights/archive-google-search-ai-mode-march-2025/) ## More information - [Documentation index](https://rangoon.ai/llms.txt) - [AI access and policies](https://rangoon.ai/ai/) - [Source repository](https://github.com/hypler-dev/rangoon)