go-adk

Expert guidance for developing agents with google.golang.org/adk (Go ADK).

When to trigger

• The user mentions Go ADK, google.golang.org/adk, adk-go, or asks how to build agents in Go.
• The task involves ADK concepts like llmagent, tools, callbacks, sessions/state/memory, workflow agents, streaming, MCP, A2A, ADK web/API runtime, launchers, deployment, evaluation, or safety controls.

Core rules

• Treat references/llms-index.md as the required ADK coverage map.
• Target the current stable Go ADK v1.x surface; as of May 5, 2026, use v1.2.0 as the default baseline unless the repo pins an older tag.
• Prefer official ADK Go APIs, package docs, and examples over ad-hoc wrappers.
• Follow existing repository patterns first (imports, launcher style, layout, env handling).
• For version-sensitive behavior, check package docs and release/docs pages before giving definitive guidance.
• Prioritize Go-specific ADK docs first; if a feature is documented only in another SDK doc, call that out explicitly and avoid presenting it as established Go API.
• Keep agent names unique and never use user as an agent name.
• Use concise Description fields so delegation and tool selection remain reliable.
• Treat ADK Web as development-only unless the user explicitly asks for production runtime choices.
• Do not mix older pre-v1 snippets with current v1 launcher/runtime patterns in the same answer.