Repository navigation
Tags: google/agents-cli
Tags
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. - #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`. - #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. - #61 - Installed extensions no longer print a warning on every command. A notice appears only when a command overridden by an extension runs. - #91
Release v1.8.0 - New flag for`agents-cli scaffold upgrade`: `--force`. A fallback for when the 3-way merge cannot run or leaves too many conflicts, similar to the existing flag for `agents-cli scaffold enhance`. It generates only the new template and overwrites the scaffolding files: - Agent code, config files and files you own are kept: your tests, custom eval metrics, eval datasets, READMEs, agent guidance files, `.gitignore`, `deployment_metadata.json` and Terraform `env.tfvars` files. - Dependencies are merged as a union. For a dependency in both files the template's version wins, and dependencies only your project has are kept. - `agents-cli scaffold upgrade` keeps your Terraform `env.tfvars` files instead of treating them as template files. - `agents-cli scaffold upgrade` and `agents-cli scaffold enhance` stop with an error when writing the merged dependencies fails. Previously they reported success and stamped the new version, so a rerun said "already at version" and could not retry. - `agents-cli run --mode a2a` sends messages and your bearer token only to the `--url` host, not to the endpoint declared in the agent card. - #46 - Two concurrent `agents-cli deploy` deploys no longer overwrite each other's deployment state. - #76 - Clarified the documentation on when to use `agents-cli infra single-project --apply` for deployments. - #79 - Generated CI/CD Terraform for Cloud Build now waits for the CI/CD service account's IAM grants to propagate before creating build triggers, so the first push after `agents-cli infra cicd` no longer fails on missing permissions. - Generated CI/CD Terraform grants Artifact Registry read access on the app's own repository instead of the whole CI/CD project. Destroying one project's infrastructure no longer breaks image pulls for other projects sharing the CI/CD project. A deploy project that relied on the project-wide grant to read another repository loses that access. - `agents-cli deploy` prints pod state, pod descriptions and namespace events when a GKE rollout does not finish. - Changed the formatting of some error messages so that they stand out more. - Updated the ADK version in scaffolded projects to `google-adk>=2.9.2,<3.0.0`. - Added experimental usage telemetry, off by default. Enable it with `AGENTS_CLI_EXPERIMENTS='{"cli_telemetry": true}'`. It writes one log entry per command to your own Cloud project, with the command, exit code, error class, duration, and CLI, Python and OS versions (but not arguments). Opt out with `AGENTS_CLI_TELEMETRY=0` or `DO_NOT_TRACK=1`.
Release v1.7.0 - **Live (voice) agents now work in `run` and `eval`.** Pass `--mode adk_live` wherever you already pass `--mode adk`: - `agents-cli run --mode adk_live` sends a prompt over ADK's `/run_live` WebSocket, against a local server or any deployment target. A turn that answers only in audio says so instead of printing nothing. - `agents-cli eval generate` and `agents-cli eval run` play each case over one persistent Live socket, with the same dataset format, trace output and grading as the SSE path. - The `gemini-3.8-live` models answer one prompt with several model turns. The CLI reads the end of a turn from `interactionStatus` instead of stopping at the first `turnComplete`. - The bundled skills cover Live: an ADK Live reference, which models support it, and how to deploy a voice agent. - `agents-cli run --mode a2a` talks A2A to the local server. A local run used to ignore `--mode` and always use ADK SSE. - `agents-cli deploy --ingress` sets Cloud Run ingress to `all`, `internal` or `internal-and-cloud-load-balancing`, so a deploy works in a project where `constraints/run.allowedIngress` rejects a public service. - #87 - `agents-cli deploy` updates the Agent Runtime engine whose resource id is recorded in `deployment_metadata.json`, and scans display names only when no id is recorded. A deleted engine, a display name that no longer matches, or a scan that finds duplicates stops the deploy instead of mutating the wrong engine. - #75 - `agents-cli deploy` and scaffolded Terraform both set `identity_type = SERVICE_ACCOUNT` on the Agent Runtime engine, so an agent keeps its service account when Agent Runtime changes that default to Agent Identity. - `agents-cli scaffold create --agent <remote URL>` handles symlinks again. Since 1.4.1 every symlink in a remote template was dropped, so a template that shared a library across variants scaffolded a project that failed at import. Links inside the cloned repo are copied as real file contents, and a link pointing outside it stops the scaffold with an error. - #89 - The generated Cloud SQL password no longer lands in Terraform state. State lives in `gs://{cicd_project}-terraform-state`, whose default IAM let anyone with Viewer on the CI/CD project read the prod database password. Generated Terraform now needs Terraform 1.11.0 or later. - Scaffolded projects need `google-adk>=2.8.0`. 2.7.x does not emit `interactionStatus`, so a Live turn boundary falls back to a heuristic there. The `<2.9.0` cap from 1.6.1 is unchanged. - The deprecated `--trace-to-cloud` alias is gone from `agents-cli playground` and `agents-cli run`. Use `--otel-to-cloud`.
Release v1.6.1
- **ADK Go is now available to everyone (Preview).** The `adk_go` template ("Go agent with A2A") now appears in `agents-cli scaffold create` with no experiment override, and Go projects get the toolchain Python already has:
- Deploy to Agent Runtime, Cloud Run and GKE, with session methods exposed to `agent_engines.get()` clients.
- CloudSQL, Agent Platform and in-memory session services.
- Prompts and responses in BigQuery Agent Analytics, and telemetry through OTLP.
- CI/CD templates at parity with Python.
- The bundled skills cover Go and Python.
- Scaffolds now default to `gemini-3.8-flash`.
- Pin `google-adk` below 2.9.0. On 2.9.0 a Cloud Run agent's prompts and responses stopped reaching BigQuery Agent Analytics, leaving `completions_view` empty.
- `agents-cli scaffold create` no longer asks for a region when the deployment target is `none`.
- The one-off `agents-cli run` no longer prints stop and resume hints for a server it did not leave running.
- `agents-cli deploy` prints how to talk to a Cloud Run agent once the deploy finishes.
- `agents-cli deploy` can change the identity type on an existing agent.
- `agents-cli deploy` now reports the correct identity after a deploy, instead of the wrong principal for agents using Agent Identity.
- Exclude vendored extensions from the deploy payload, where they could add megabytes to every deploy.
- `agents-cli infra single-project` now correctly enables the Service Usage API, so a new project bootstraps without enabling it by hand.
- Fix remote ADK samples generating two agent directories and an unbuildable project.
- Scaffolded Dockerfiles install uv from a pinned image instead of `pip install`.
- `agents-cli run` and `agents-cli eval` no longer stop a background server they only borrowed.
- #71
- Startup and version notices now go to stderr, so `--json` output stays machine-readable.
- #69
- `agents-cli eval generate` no longer silently drops per-case session state.
- #52
- `agents-cli run --mode a2a` now shows status updates, errors and empty turns instead of staying silent.
- The `run` resume hint includes `--url` and the other routing flags.
- `agents-cli info --json` reports `root_agent_name`.
- `agents-cli extension add` no longer copies ignored files from a `local@` source.
- Fix the macOS-only `sed` in the Starter Pack migration guide and spell out the dry-run and apply steps.
- #78
Release v1.5.0 - **Extension system with a LangChain template.** `agents-cli` can now be extended with custom commands and add-on agent templates, shipped with a LangChain extension and authoring guides. Extensions install from GitHub, other git hosts (including self-hosted and enterprise servers), or a local path for development. - Add `agents-cli infra show` to inspect the Terraform configuration provisioned by `agents-cli infra single-project`. - Add `--update-only` to `agents-cli deploy`, so a deploy updates an existing Agent Runtime engine instead of creating a duplicate. - Add a `--labels` flag to `agents-cli deploy` to tag Agent Runtime and Cloud Run deployments. - Add `--qps` to `agents-cli eval` that controls the request rate instead of being throttled to the default value. - Name the scaffolded root agent after its project instead of a generic default. - `agents-cli deploy` now retries throttled Agent Platform calls. - `agents-cli create` now reports precondition failures as clear errors instead of exiting successfully or printing a traceback. - #68 - Fix background server reuse ignoring the requested session mode. - #70 - Fix `reasoning_engine_adapter` streaming returning an empty response. - #80 - Prevent multi-region deployments in scaffold and deploy. - #81 - Give a clear error for malformed project manifests instead of silently defaulting or printing a traceback. - #74 - Fix stale command references in docs and CLI hints. - #77 - Scaffolded A2A agents now forward tool calls and responses to clients, not just text. - `agents-cli setup` now works without network or git access, with skills bundled into the package. - Fix a Windows failure loading a scaffolded project whose config points at a local path.
Release v1.4.1 - Scaffolds now default to `gemini-3.7-flash`. - `agents-cli eval generate` no longer fails to generate traces for some agents. - `agents-cli deploy` now defaults to `--min-instances 0` (was `1`) on Agent Runtime and Cloud Run, so that idle dev and demo agents don't take up resources. - `agents-cli scaffold upgrade` now creates a project backup before applying changes, just like `agents-cli scaffold enhance`. - Fixed `npx skills find` to use the pinned `skills` version. - #72 - Fixed an arbitrary file write vulnerability in `agents-cli scaffold create`. - #50
Release v1.4.0 - Add Agent Gateway support to `agents-cli deploy` - Improve A2A-on-Agent-Runtime and MCP Agent Registry guidance in skills - Use token-based context compaction in ADK cheatsheet - Add held-out case guidance during iteration to the eval skill - Remove built-in feedback endpoint, add guidance on building a feedback mechanism to the observability skill instead - Display project language in `agents-cli info` - Use $GH_TOKEN and $GITHUB_TOKEN environment variables as fallbacks for `--github-pat` - #18 - Populate class_methods contract on agent_runtime deploy - #55
Release v1.3.0 - Update to use A2A 1.0 throughout, with a compatibility layer for A2A 0.3 clients - Improve retry for Cloud Run deploy - Streamline retry handing for `infra cicd` command - Fix `npx skills` output formatting during setup and update - Print Cloud Logging URL at Agent Runtime deploy start - Add --concurrency and --header flags to eval generate/run - Tweak messages around `--session-type` when used with `agent_runtime`
PreviousNext