GoogleToni Klopfenstein, Sampath Kumar MaddulaAnnouncement
Build reliable multi-agent applications with ADK Go 2.0. Discover our new graph-based workflow engine, built-in human-in-the-loop, and dynamic orchestration
Summary
ADK for Go 2.0 introduces a graph-based workflow engine for composing multi-agent applications whose execution can classify, branch, fan out, gather results, pause for human input, retry, and loop. Graphs consist of typed nodes and routed edges, with constructors for functions, emitting functions, agents, tools, joins, parallel workers, state-bound nodes, dynamic orchestration, and nested workflows; a scheduler handles concurrency, persistence, backpressure, cancellation, and resumption. Its built-in human-in-the-loop primitive validates responses, supports handoff or re-entry, and can resume durably after process restarts, while agent modes and a unified node runtime align single agents with full graphs. The release is highly additive for ADK 1.0 users, though context and event APIs require mechanical migrations, and it provides workflow examples for basic, routing, dynamic, HITL, and complex graphs.
Context
Production agent applications often require classification, branching, parallel specialist work, human approval, retries, and loops. The post says expressing these patterns as ad-hoc control flow becomes brittle, motivating a graph-based orchestration model for Go.
Approach / What changed
ADK for Go 2.0 adds a graph-based workflow engine built from typed nodes and routed edges, with a scheduler for concurrency, state persistence, pausing, resumption, retries, timeouts, and cancellation. It also adds dynamic nodes, built-in human-in-the-loop support, LLM agent modes, and a unified runtime and context model.
Takeaways
A graph is an agent and runs through the existing runner, launcher, and console; no special harness or new server is required.
Human-in-the-loop requests can use handoff or re-entry, validate responses against a schema, and resume idempotently after process restarts or across runtimes.
ADK 1.0 migrations include changing node and node-function parameters to agent.Context, updating session.NewEvent calls, and accounting for richer event fields.
Source and freshness
- Source
- developers.googleblog.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.