Google Developers announced on its blog that the google/adk-recipes repository now serves as the single source of truth for Agent Development Kit resources.confirmed The restructured library replaces the previous google/adk-samples and organizes content into three distinct layers. This change aims to streamline workflows from initial scaffolding to full deployment on Google Cloud infrastructure.
The figures
- Three top-level folders: core/, plugins/, and contrib/
- One specification version: Agent Plugins v1.0.0reported
- Five languages supported in the contrib/ layer
- Four deployment targets: Cloud Run, Agent Runtime, Agent Garden, and Gemini Enterprise app
Behind the figures
The structure is defined by the repository's directory layout, as described in the Google Developers blog post. The core/ folder contains reference patterns curated by the Agents CLI and DevRel teams. The plugins/ folder holds installable vertical skills, while contrib/ contains end-to-end deployable services. Each recipe ships with a validated manifest.yaml and an AGENTS.md file.
What it means for your stack
Developers can now scaffold long-horizon memory agents directly from the terminal using the Agents CLI. The CLI reads from the core/ layer to provide production templates. Additionally, developers can install retail vertical skills, such as product search or virtual try-on, into coding assistants with a single line of code. These skills are packaged as Plugin Recipes.
Building on this
Inference engineers can build agents that discover and install recipes automatically via coding assistants. The AGENTS.md files are written primarily for AI coding assistants, not just human readers. This allows agents to scaffold, validate, and submit recipes end-to-end. For example, the Horizon reference harness uses Agent Platform Sandboxes for per-user isolation. It also leverages Memory Bank for durable memory and Agent Platform Sessions for state management.
Why it matters
- Machine readability allows coding assistants to parse and apply recipes without manual intervention.
- The Agent Plugins v1.0.0 spec standardizes how vertical skills like retail search are packaged.
- CI enforces standards on every pull request, ensuring recipe consistency across the ecosystem.
- Developers can deploy services to multiple targets, including Cloud Run and Gemini Enterprise.
Topics: Google, ADK, Agent Development, Cloud Run, AI Agents
Updated
Ask the article
Local keyword search of this article; no generated answers.Which of these is confirmed?
Check the answer
Google Developers announced on its blog that the google/adk-recipes repository now serves as the single source of truth for Agent Development Kit resources.
The matched primary source and announcement wording support the confirmed label.
Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
What replaced the google/adk-samples repository?
The google/adk-recipes repository is the restructured successor that now serves as the single source of truth.
How do coding assistants interact with these recipes?
They read AGENTS.md and manifest.yaml files to discover, install, and use recipes automatically.
Which infrastructure components are used in the Horizon example?
Horizon uses Agent Platform Sandboxes, Memory Bank, and Agent Platform Sessions.
Connected stories
Reading receipt
- The repository unifies ADK resources into core, plugins, and contrib folders.
- Every recipe includes a manifest.yaml, AGENTS.md, and machine-readable metadata.
- Plugins conform to the Agent Plugins v1.0.0 specification for vertical skills.