Google Expands ADK to Go, TypeScript, Java and Kotlin

Google has expanded its open-source Agent Development Kit with native support for Go, TypeScript, Java, and Kotlin. The update enables developers to build and deploy AI agents using enterprise-standard languages and runtimes instead of relying solely on…

Christopher Ort
By Christopher Ort · 4 min read
Share
Abstract illustration of multi-language AI agents built with Google ADK across enterprise runtimes
Illustration: i10X
On this page
  1. Quick Take
  2. What happened
  3. Why it matters now
  4. Who is most affected
  5. The governance and scaling angle
  6. About the analysis
  7. i10x Perspective

Google has expanded its open-source Agent Development Kit (ADK) with native support for Go, TypeScript, Java, and Kotlin on top of the original Python base. The move pulls AI agent work out of isolated data-science environments and places it inside the languages and runtimes that already power enterprise systems.

i10X Quick Take

Quick Take

  1. The news: Google’s ADK now natively supports five programming languages, breaking the traditional Python monopoly in generative AI development.
  2. The infrastructure shift: Enterprise AI is moving from isolated prototypes to distributed, multi-agent systems capable of running across web browsers, JVM applications, and Kubernetes clusters.
  3. The protocol power play: The expansion heavily leverages the Agent2Agent (A2A) protocol and Model Context Protocol (MCP) to ensure agents built in different languages can seamlessly discover each other, delegate tasks, and access enterprise databases.
  4. The competitive edge: By accommodating the tools developers already use, Google is positioning the Gemini Enterprise Agent Platform and Vertex AI as the unified orchestration layers for the next generation of multi-agent workloads.

What happened

Google has upgraded its open-source Agent Development Kit, rolling out native compatibility for Go, TypeScript, Java, and Kotlin. This expansion allows software teams to build AI agents using the languages native to their existing backend services, web applications, and Android environments, eliminating the need to force-fit Python into varied enterprise architectures.

The toolkit is deeply integrated with the Gemini Enterprise Agent Platform and Vertex AI Agent Engine. It provides the necessary command-line tooling, project scaffolding, and deployment configurations to push AI agents directly into diverse runtime environments. This includes local execution, Google Kubernetes Engine (GKE), and Cloud Run.

Beyond just language syntax, the update is designed around open interoperability. It packages native support for standardized communication protocols, enabling developers to stitch together complex, distributed agent networks rather than building monolithic AI applications.

Why it matters now

The AI industry has a deployment bottleneck: powerful LLMs are often trapped in Python-heavy prototype wrappers that struggle to mesh natively with existing Java or Go-based enterprise infrastructure. By democratizing the language requirements, Google is eliminating the friction between AI engineering and traditional software development. An organization can now deploy a frontend TypeScript agent for user interaction that seamlessly hands off complex backend processing to a high-performance Go agent.

This cross-runtime collaboration is supercharged by two critical interoperability frameworks. The Model Context Protocol (MCP) acts as a standardized bridge, securely connecting these diverse agents to external tools, APIs, and proprietary enterprise data. Simultaneously, the Agent2Agent (A2A) protocol allows agents-even those built in non-Google frameworks like LangGraph or CrewAI-to discover capabilities and delegate tasks to one another.

Strategically, this is Google maneuvering to own the multi-agent orchestration layer. By providing the tools to build, govern, and deploy a multi-language swarm of agents, Google Cloud is cementing Vertex AI as the ambient event mesh for enterprise intelligence, targeting CTOs who are weary of fragmented AI tooling.

Who is most affected

The immediate beneficiaries are enterprise platform engineering teams and traditional software developers who have historically been sidelined by the Python-centric nature of the generative AI boom. Organizations heavily invested in JVM or Go architectures can now integrate LLM-driven intelligence natively without maintaining parallel tech stacks, bridging disparate runtimes, or entirely retraining their engineering workforce.

StakeholderImpactWhy
Enterprise CTOsUnified AI infrastructureThey can govern, monitor, and scale AI agents within their existing security perimeters and cloud deployments.
Software DevelopersNative AI integrationThey are no longer required to learn Python to build, debug, and orchestrate production-grade AI agents.
AI Platform TeamsSimplified orchestrationStandardized A2A and MCP protocols allow agents from different internal teams or external vendors to collaborate securely.

The governance and scaling angle

Moving beyond language diversity, this expansion signals a maturation in how multi-system agents are governed in production. When agents communicate across languages using A2A via the Vertex AI Agent Engine, enterprises gain access to centralized observability tools like the Agent Registry and Agent Gallery. This means a sprawling corporate network of diverse, autonomous agents can finally be monitored for context management, session security, and evaluation metrics as a cohesive production unit, rather than a fractured set of API calls.

About the analysis

Researched and written with AI assistance under the editorial responsibility of the i10X News team. The title image is an AI-generated illustration. Read our AI Use Policy. Spotted an error? Request a correction.

This is an independent i10x analysis based on official product documentation, developer guidelines, and industry reporting, curated to help technical leaders, CTOs, and platform engineers navigate the evolving AI infrastructure landscape.

i10x Perspective

The era of the monolithic, Python-exclusive AI agent is effectively over. Google’s expansion of the ADK reflects a critical market reality: for AI to truly infiltrate the enterprise, it must conform to the infrastructure that already runs the world, not the other way around. As protocols like A2A and MCP standardize how intelligence communicates across language barriers, the next major AI frontier won’t be about who builds the smartest single model, but who can orchestrate the most resilient, multi-lingual swarm of agents.

Christopher Ort

Christopher Ort

Christopher Ort handles SEO, AI agent workflows and PR & partnerships at i10x.ai, the all-in-one AI workspace built by i10X Global Pte. Ltd. in Singapore. He is a graduate of Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU). He is the author of “The Style Penalty”, a study published on SSRN that analyses 1,576 evaluation decisions by four frontier AI models to show how AI-written CVs fare in automated hiring screens; the research has been covered by heise online and t3n.

Timeline

What happened before

  1. Release

    Gemini 4 Argon

    1.05M context · $2 / $10 per 1M tokens

    Google's most capable model for complex coding, agentic, math and science tasks.

    ai.google.dev (source, opens in a new tab)
  2. Release

    Gemini 3.8 Flash

    1.05M context · $0.75 / $3.75 per 1M tokens

    ai.google.dev (source, opens in a new tab)
  3. Release

    Gemini 3.7 Flash

    1.05M context · $0.75 / $3.75 per 1M tokens

    ai.google.dev (source, opens in a new tab)
  4. Release

    Gemini 3.6 Flash & 3.5 Flash-Lite

    1.05M context · $0.75 / $3.75 per 1M tokens

    ai.google.dev (source, opens in a new tab)
  5. Partnership

    Google to pay SpaceX $920M a month for Colossus compute (~$30B through 2029)

    With Google · Compute · $30B

    Per SpaceX's SEC filing: about 110,000 NVIDIA GPUs from October 2026 to June 2029, ramping through September at a reduced fee; either side may terminate after Dec 31, 2026 with 90 days' notice (CNBC, Bloomberg).

    cnbc.com (source, opens in a new tab)
Full Google timeline ›

Editor's picks

  1. Anthropic IPO Filing Reveals Extreme AI Safety Risks
  2. Grok Imagine Odyssey Pilot Exposes AI Video Limits
  3. Anthropic Files S-1 for Nasdaq IPO Under Ticker ANT
  4. Jakarta Agentic AI Milestone Delivers Standardized AI Agents for Java
  5. llm-deepseek Serialization Bug Replays Text After Tool Use