go agent-orchestration workflow-graph human-in-the-loop state-persistence

ADK for Go 2.0 adds graph-based workflow engine

Graph-first orchestration replaces ad-hoc control flow for multi-agent apps, with built-in human-in-the-loop and durable state that survives process restarts.

Summary

Developers can now express complex agent branching, fan-out, approval gates, and retry logic as declarative graphs instead of brittle imperative code. State persists across restarts and runtimes, eliminating manual orchestration plumbing.

Why it matters

Implementation verdict

Replaces manual agent composition and custom orchestration layers. Requires Go 1.22+ (iter.Seq2) and adoption of graph construction API. Ready now for new projects; existing ADK 1.x agents are compatible. Worth migrating if you're building multi-step workflows with branches or HITL.

Sources

1.Production agents must classify, branch, fan out, ask a human to approve something, retry on failure, and loop until done
2.A graph is an agent. That wf is just an agent.Agent. It runs in the same runner, launcher, and console you already use — no special harness, no new server
3.the workflow durably waits for the answer
4.a workflow can resume after a process restart, or even across different runtimes, because the interrupt format is shared with Python ADK

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs