adk-python
* **`Agent`**: The core intelligent unit. Can be `LlmAgent` (LLM-driven) or `BaseAgent` (custom/workflow). * **`Tool`**: Callable function providing external…
Recipes live in [google/adk-samples](https://github.com/google/adk-samples). **`core/python/`** is the curated tier — canonical ADK patterns maintained by the agents-cli team.
$ npx -y skills add google/agents-cli --agent claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Recipes live in [google/adk-samples](https://github.com/google/adk-samples). **`core/python/`** is the curated tier — canonical ADK patterns maintained by the agents-cli team.
Recipes live in [google/adk-samples](https://github.com/google/adk-samples). **`core/python/`** is the curated tier — canonical ADK patterns maintained by the agents-cli team.
**Reading this page is not studying a recipe.** Every `core/` recipe ships an **`AGENTS.md`** — intent, a ranked "study in this order" file tour, what to copy as-is versus what is recipe-specific, and the gotchas. Until you have opened it you are answering from memory.
**Study and adapt — don't scaffold from a recipe.**
[ -d /tmp/adk-samples ] || git clone --filter=blob:none --depth 1 --sparse \ https://github.com/google/adk-samples /tmp/adk-samples cd /tmp/adk-samples git sparse-checkout add core/python/<recipe> cat core/python/<recipe>/AGENTS.md
(The `--agent adk@<name>` scaffold shortcut reaches only the legacy `python/agents/` tree, not `core/`.)
Capabilities below are **not** scaffold flags — they come from studying a recipe and adapting it.
| You need | Study | |---|---| | Retrieval / search over your own documents (RAG) | `rag-agent-search` (managed ingestion) · `rag-vector-search` (custom chunking + embeddings) | | Running shell commands or Python on a user's behalf; a sandboxed, isolated or per-user environment or workspace | `long-horizon-harness` | | Agent-loadable skills — `SKILL.md` folders discovered at runtime, rebound mid-session, promoted and demoted from memory | `long-horizon-harness` | | Long-running autonomy — works across days, resumes, unattended, compacts context | `long-horizon-harness` | | Approval gate, escalation or human sign-off before a risky, high-value or irreversible action (human-in-the-loop) | `long-horizon-harness` (durable, mid-turn) · `ambient-expense-agent` (workflow pause) · `deep-search` (plan approval) | | Memory across conversations | `cross-session-memory` (the primitive) · `long-horizon-harness` (self-improvement loop built on it) | | Blocking harmful content or risky calls — moderation in one place, covering a coordinator and every sub-agent without editing them | `safety-plugins` (runner-wide plugins) · `long-horizon-harness` (per-tool guard chain + exfil detection) | | Per-user credentials the model must never see | `long-horizon-harness` | | OAuth user consent to act on a user's data | `oauth-user-consent-flow` | | Sub-agent delegation with isolated context windows | `long-horizon-harness` | | No chat interface — records or messages land on a queue and are processed automatically; event-driven, scheduled, batch or headless worker | `ambient-expense-agent` (Pub/Sub queue consumer) · `long-horizon-harness` (routines + scheduler) | | Iterative research with cited sources | `deep-search` | | Generating images or video — product photography, a model wearing the item (virtual try-on), 360° spins, background replacement — and MCP toolsets | `genmedia-for-commerce` | | A2A interop, incl. Gemini Enterprise client quirks | `long-horizon-harness` |
In Phase 1, clone the recipes named above and read `/tmp/adk-samples/core/python/<recipe>/AGENTS.md` before you write any code. During Phase 0, naming them in the spec is enough — the clone waits for approval. A bare how-question has no spec to wait for: clone before you answer it.
These nine are the **complete** set of `core/` python recipes. If a capability isn't listed here, there is no core recipe for it — don't guess at a plausible name (`core/python/code-execution` and `core/python/human-in-the-loop` do not exist). Check `contrib/` or build it yourself.
skills, cross-session memory with a self-improvement loop, layered tool guardrails, sub-agent delegation with durable HITL, and per-user secrets. Its `AGENTS.md` maps each interface to the real function that implements it, so lift one pattern without adopting the whole harness.
fully-managed GCS Data Connector: drop files in a bucket, no ingestion code to maintain.
BigQuery staging; embeddings auto-generated server-side).
Bank: written after each turn, recalled at the start of a later one.
flow; the same code path works in local ADK Web and in production Gemini Enterprise.
The CLI and skills that turn any coding assistant into an expert at creating, evaluating, and deploying AI agents on Google Cloud.
Repo: google/agents-cli
* **`Agent`**: The core intelligent unit. Can be `LlmAgent` (LLM-driven) or `BaseAgent` (custom/workflow). * **`Tool`**: Callable function providing external…
Requires `google-adk >= 2.0.0`. Python only. Requires **Python >= 3.11**. The `Workflow` class itself does not support Live Streaming (`Runner.run_live`) — the…
**Assumes `/google-agents-cli-scaffold` scaffolding.** If your project isn't scaffolded yet, see `/google-agents-cli-scaffold` first.
Invoke your agent as a BigQuery Remote Function for batch inference over table rows. This requires a custom `POST /` endpoint since BQ cannot use URL paths.
**Best for:** Production applications, teams requiring staging → production promotion.