<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>adk on Alan Blount | AI/ML Engineer at Google</title><link>http://zeroasterisk.com/tags/adk/</link><description>Recent content in adk on Alan Blount | AI/ML Engineer at Google</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 01 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://zeroasterisk.com/tags/adk/index.xml" rel="self" type="application/rss+xml"/><item><title>Why We Built ADK 2.0</title><link>http://zeroasterisk.com/2026/07/why-we-built-adk-2.0/</link><pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate><guid>http://zeroasterisk.com/2026/07/why-we-built-adk-2.0/</guid><description>Why We Built ADK 2.0 Originally published on Google Developers Blog - July 1, 2026, co-authored with Swapnil Agarwal and Frank Guan.
Next-gen agent development is here. ADK 2.0 is a ground-up evolution of the Agent Development Kit, aimed at making it far easier to build reliable, production-grade multi-agent applications.
Why This Matters Building agents at scale exposes gaps that don&amp;rsquo;t show up in prototypes: orchestration across many agents, human-in-the-loop checkpoints, dynamic routing, and resilience against failures.</description></item><item><title>Announcing ADK for Go 2.0</title><link>http://zeroasterisk.com/2026/06/announcing-adk-for-go-2.0/</link><pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate><guid>http://zeroasterisk.com/2026/06/announcing-adk-for-go-2.0/</guid><description>Announcing ADK for Go 2.0 Originally published on Google Developers Blog - June 30, 2026, by Toni Klopfenstein and Sampath Kumar Maddula.
ADK for Go 2.0 introduces a brand-new graph-based workflow engine for composing complex, multi-agent Go applications, with idiomatic support for human-in-the-loop orchestration, dynamic routing, and built-in resilience — all on a unified runtime.
Why This Matters Go&amp;rsquo;s strong concurrency model pairs well with graph-based agent orchestration, and this release makes it much more natural to build production multi-agent systems in Go rather than bolting agent logic onto ad hoc goroutine pipelines.</description></item><item><title>Building Agents with the ADK and the New Interactions API</title><link>http://zeroasterisk.com/2025/12/building-agents-with-the-adk-and-the-new-interactions-api/</link><pubDate>Thu, 11 Dec 2025 00:00:00 +0000</pubDate><guid>http://zeroasterisk.com/2025/12/building-agents-with-the-adk-and-the-new-interactions-api/</guid><description>Building Agents with the ADK and the New Interactions API Originally published on Google Developers Blog - December 11, 2025, co-authored with Mike Smith and Xiang (Sean) Zhou.
The landscape of AI development is shifting from stateless request-response cycles to stateful, multi-turn agentic interactions. The new Interactions API lets you power ADK agents or connect A2A systems directly to the Gemini Deep Research Agent.
Why This Matters Stateful, multi-turn interaction patterns are exactly where agent memory systems earn their keep — this API gives ADK and A2A a standard way to plug into long-running, stateful agent experiences.</description></item><item><title>Delight Users by Combining ADK Agents with Fancy Frontends Using AG-UI</title><link>http://zeroasterisk.com/2025/12/delight-users-by-combining-adk-agents-with-fancy-frontends-using-ag-ui/</link><pubDate>Thu, 11 Dec 2025 00:00:00 +0000</pubDate><guid>http://zeroasterisk.com/2025/12/delight-users-by-combining-adk-agents-with-fancy-frontends-using-ag-ui/</guid><description>Delight Users by Combining ADK Agents with Fancy Frontends Using AG-UI Originally published on Google Developers Blog - December 11, 2025.
The ADK and AG-UI integration lets developers pair a powerful ADK-based agent backend with a flexible, interactive frontend — combining Google&amp;rsquo;s Agent Development Kit with the AG-UI protocol to build richer, more responsive AI applications.
Why This Matters Backend agent logic and frontend UX are often built by separate teams with separate toolchains.</description></item></channel></rss>