agents-cli

Release v1.12.0

• ADK Go is now Generally Available. The adk_go template is out of Preview: it is stable, production-ready and supported on the same terms as adk_python. This release also brings:
  • agents-cli create --agent <template> supports ADK Go v2 templates whose manifest.yaml declares language: go. Templates built for other ADK Go versions are rejected. A declared language that contradicts the base template (or --base-template) fails with an error explaining how to fix it.
  • The server e2e tests in new ADK Go projects time out after 120s instead of 60s, so multi-step agents no longer time out.
• The Python agent template is now adk_python, selected with --agent adk_python (or -a adk_python). adk still works as an alias. New projects record adk_python in agents-cli-manifest.yaml, and upgrading a project recorded as adk records adk_python too. Enhancing or upgrading these projects requires this CLI version or newer.
• New experimental Claude Agent SDK extension. Create a project with agents-cli scaffold create --agent google/agents-cli/extensions/claude/template@<version>, or migrate an existing agent with scaffold enhance and that template. It deploys to Agent Runtime or Cloud Run over A2A, calls Claude on Gemini platform only, and comes with Cloud Trace, Cloud Logging, Cloud Monitoring, optional BigQuery Agent Analytics and Cloud SQL sessions. playground, eval dataset synthesize and eval optimize aren't supported, and publish gemini is refused on Agent Runtime.
  • On Agent Runtime, these agents also serve :query (async_create_session) and :streamQuery (async_stream_query), so an ingress Agent Gateway can govern them (for example with Model Armor) and agents-cli run --mode adk works.
• The agent template directory can be a nested folder, such as src/my_agent, both in remote templates and with --agent-directory.
• agents-cli scaffold enhance <template> on a project agents-cli didn't create writes the template's files as create would, and moves each of your files it replaces (such as pyproject.toml, README.md, Dockerfile, .env) to .agents-cli-original/, keeping its path. Your other files stay where they are. Port what you need from the folder, then delete it; enhance won't run again while it exists. New projects' .gitignore and .gcloudignore exclude the folder.
• Extension templates can set settings.session_types, so create offers and accepts only those session types, with the first as the default. A template whose list is empty or names an unknown session type is rejected.
• agents-cli scaffold enhance --dry-run exits with code 2 (was 0) when combined with --force, when run with -y and no override flags, or when run without a saved agents-cli-manifest.yaml.
• Cloud Run projects run their Cloud Run service on the hashicorp/google-beta provider, pinned to ~> 8.7. Other resources keep hashicorp/google ~> 7.28. Existing projects pick it up through agents-cli scaffold upgrade; if terraform init then reports a locked google-beta older than 8.7, run terraform init -upgrade once.
• The server e2e tests in new Python projects time out after 120s instead of 60s, so multi-step agents no longer time out.
• agents-cli deploy --dry-run for Agent Runtime prints the plan even when a check fails. It still exits with code 1.
• agents-cli deploy --dry-run for Agent Runtime warns that it could not verify the secrets when the Secret Manager API is disabled, instead of skipping the check silently.
• agents-cli deploy --dry-run also validates a Cloud Run deployment against Google Cloud.
• A malformed --env-vars, --secrets or --labels value fails before the project prompt.
• A failed agents-cli publish gemini reports the API's reason (for example a SERVICE_DISABLED message with the enable link) instead of a bare HTTP error.
• A failed terraform step in agents-cli infra exits with a short error naming the step and ho

Release v1.11.0

• Breaking: The adk@<name> shortcut has been removed. Pass the recipe's GitHub URL to agents-cli create instead, and browse recipes at https://github.com/google/adk-recipes.
  • The scaffold's "Browse ADK recipes" option lists recipes from both core/python/ and contrib/python/ in google/adk-recipes.
  • Projects created with adk@ still upgrade. Their base_template is rewritten to the recipe URL on the first applied change.
• New projects use google-adk>=2.12.0 and google-cloud-aiplatform>=2.2,<3. Agent Runtime projects also depend on google-cloud-agentplatform, and the LangChain extension template moves to google-cloud-aiplatform>=2.2,<3.
• agents-cli deploy to Agent Runtime registers the ADK artifact methods (async_save_artifact, async_load_artifact, and others).
• agents-cli deploy to Agent Runtime shows the last 40 lines of the build log when a build fails, instead of only "Build failed". deploy --status shows it too.
• agents-cli's uv commands use public PyPI even when a machine-wide uv config points at a mirror, so deploy no longer breaks. agents-cli install warns when uv.lock uses a mirror and shows the command to re-lock. install --locked now fails on such a lock. Scripts and CI jobs that run install --locked may need an update.
  • https://github.com/google/agents-cli/issues/95
• agents-cli create finds the agent code in any remote template, not only adk-recipes ones. When both app/ and a folder-named package exist, app/ wins; use --agent-directory to pick the other. A top-level agent_directory in a template's agents-cli-manifest.yaml is now respected.
• LangChain agents are now named after your project, or the name you pass with --root-agent-name, like ADK agents.
  • Template authors can list files under render_files in .template/templateconfig.yaml. Placeholders such as the agent name are then filled in in those files when a project is created.
• Traces from LangChain agents now record which conversation each request belongs to (gen_ai.conversation.id), so you can follow a conversation across requests, as you already can for ADK agents.
• agents-cli run --mode a2a shows why an agent's task failed, was rejected or was canceled ([error]: <reason>) instead of "(no response content)".
• ADK Go agents no longer lose replies for turns that take longer than 15 seconds on /run or A2A.
• The Cloud Build pipelines and Dockerfile in generated ADK Go projects retry Go module downloads, so a dropped connection to the Go module proxy no longer fails the build.
• ADK Go projects include only the session backend chosen at creation time.
• agents-cli scaffold upgrade stops instead of reporting success when it cannot build the template of the project's original version. It shows why, and suggests --force when that can help.
• agents-cli scaffold upgrade no longer warns about a legacy eval file that an earlier, stopped upgrade already migrated.
• agents-cli setup --workspace lists each installed skill's folder once.
• Extensions can no longer override agents-cli info, login, setup or update.
• agents-cli --help, the docs and error hints show create commands that work as written: -i to choose options in prompts, -y to accept the defaults (adk template, agent_runtime target).
• Warnings print as ⚠️ Warning: <message> with a yellow prefix on stderr. Some warnings that used to go to stdout now go to stderr. Scripts that read warnings from stdout may need an update.
• Errors that agents-cli logs print with the same red ❌ Error: prefix as other errors, and --debug output prints as dim Debug: … lines.
• agents-cli no longer prints the google-auth quota-project warning or google-genai's automatic function calling advice. eval run no longer prints "Could not obtain credentials" when it talks to the local agent server.

Release v1.10.0

• New projects use Agent Identity by default. agents-cli scaffold create records agent_runtime_identity_default: agent_identity. Then agents-cli deploy creates the Agent Runtime agent under its own Agent Identity principal, and the generated Terraform (infra single-project, infra cicd) does the same. To keep a service account, pass --agent-runtime-identity-default service_account to scaffold create or scaffold enhance. Existing projects are not changed: if the setting is missing, it reads as service_account, and scaffold upgrade does not migrate it.
  • deploy uses this default only when it creates a new agent. A redeploy without --agent-identity or --no-agent-identity does not change the identity of an existing agent.
• Extensions can ship skills. An extension declares skills in the skills: field of agents-cli-extension.yaml:
  • agents-cli extension add copies them to <project>/.agents/skills/, or to ~/.agents/skills/ with --global.
  • agents-cli extension update replaces them with the new version's skills and lists the skills it removed.
  • agents-cli extension remove deletes them. The new --global flag removes the user-scope install.
  • agents-cli install restores the skills of every recorded extension.
  • A skill folder copied by an extension is managed by that extension, and manual modifications to it might be overwritten.
• agents-cli extension update keeps the old local copy when it refuses a new version or a copy fails.
• New agents-cli deploy flags for Agent Runtime and Cloud Run: --remove-labels KEY,... and --clear-labels. New aliases that match gcloud run deploy: --update-labels, --update-secrets and --env-vars.
• agents-cli deploy now rejects --iap, --port, --service-account and --cluster-name on targets that ignored them. Before, they were silently ignored. Scripts that pass them may need an update.
• agents-cli run fails with Agent run failed: <reason> and a non-zero exit code when the ADK stream sends an error. Before, the run looked successful.
• agents-cli scaffold create shows the dependency changes, like enhance and upgrade do.
• agents-cli scaffold create keeps the detected project in .env when credential checks fail, instead of writing the your-gcp-project-id placeholder. It also warns when --session-type is ignored for --deployment-target none.
• agents-cli scaffold enhance creates missing config and dependency files instead of skipping them.
• Values in agents-cli-manifest.yaml are now escaped, so a quote or newline in a value no longer breaks the file. Project names are limited to a-z, 0-9 and -.
• Terminology has been adjusted in various places to use appropriate names for the Gemini ecosystem. No functional change, as old variants are kept as aliases where applicable.
• The CLI now uses google-cloud-aiplatform 2.x, and gcsfs is pinned to >=2026.10.0. The template lock files are updated.
• The bundled skills list the Ambient Quality Agent (AQuA) recipe.

Release v1.9.0

• Usage telemetry is now on by default. Each command writes one log entry to your own Google Cloud project with the command name, exit code, error class, duration, and CLI, Python and OS versions, never arguments or file contents. Its purpose is to provide users with analytics regarding their tool use, process efficiency, and help diagnose potential issues. The request also sends Google the CLI, Python and OS versions, CPU architecture and command name for usage analytics; no sensitive data is sent. Opt out with AGENTS_CLI_TELEMETRY=0 or DO_NOT_TRACK=1. agents-cli info now always shows whether telemetry is on.
• agents-cli deploy --key encrypts an Agent Runtime agent with a customer-managed Cloud KMS key (CMEK), so deploys work in projects that enforce constraints/gcp.restrictNonCmekServices. The key can only be set when the agent is created, and deploy --list shows it in a new Encryption column.
  • https://github.com/google/agents-cli/issues/83
• agents-cli deploy --dry-run checks an Agent Runtime deployment against Google Cloud: enabled APIs, the target engine, IAM permissions, actAs on the service account, and secrets. A definite problem exits with code 1, and a check that cannot run only warns. A dry run now makes read-only network calls. A real deploy is unchanged.
• agents-cli deploy reports unsupported flags in one format, <flag> is only supported for <targets> deployments (current target: <target>), and names only the flags you passed. An empty value for such a flag, such as --key "" on Cloud Run, is now rejected instead of ignored. Scripts that match the old error text may need updating.
• New ADK Python projects set GOOGLE_GENAI_USE_ENTERPRISE=true instead of the deprecated GOOGLE_GENAI_USE_VERTEXAI. Existing projects keep working: agents-cli deploy to Agent Runtime respects whichever name your .env sets. Go projects keep the old name.
• New ADK Go projects enable the gofmt and goimports formatters, so agents-cli lint reports formatting issues and lint --fix fixes them.
• Re-applying the Terraform generated by this release, for example with agents-cli infra single-project or infra cicd, no longer replaces the BigQuery log sink tables once logs have arrived. The replacement deleted every exported log. completions_view also gains a service_version column with the deployment revision. Run agents-cli scaffold upgrade to get this in an existing project.
• Scaffolded ADK projects no longer append a duplicate JSONRPC 0.3 interface to the agent card on every request to .well-known/agent-card.json.
  • https://github.com/google/agents-cli/issues/84
• A tool that exists but cannot run, such as uv.exe blocked by AppLocker on Windows, now fails with a clear error naming the tool and the OS reason instead of a PermissionError traceback.
  • https://github.com/google/agents-cli/issues/61
• Installed extensions no longer print a warning on every command. A notice appears only when a command overridden by an extension runs.
  • https://github.com/google/agents-cli/issues/91