You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE_NOTES.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,15 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
## [1.1.0] - 2026-07-10
6
+
7
+
-**Guided brainstorming for new agents.** The workflow skill's Phase 0 is now an interactive brainstorming dialogue that helps you shape an agent's spec before any code is written, and surfaces its assumptions for review when it can't ask.
8
+
-`eval generate` and `eval grade` no longer clutter output with benign third-party warnings and progress bars that never affected results. This output is still shown on failure and can be re-enabled for debugging.
9
+
- Generated projects now name the default scaffolded eval metric module `tests/eval/response_quality.py` (was `metrics.py`) to match the metric it implements.
10
+
- Broad Windows compatibility fixes across the CLI.
11
+
- Fixed a command-name typo in user-facing hints so they point to the correct `agents-cli` command.
12
+
- Refreshed the bundled skills, including pointing the RAG samples at `core/python/` in `google/adk-samples`.
13
+
5
14
## [1.0.0] - 2026-06-30
6
15
7
16
**Agents CLI is now 1.0 — Generally Available.** This is our first GA release: a stable, production-ready CLI for scaffolding, evaluating, and deploying ADK agents on Google Cloud.
@@ -58,6 +57,8 @@ Choose the right deployment target based on your requirements:
58
57
59
58
**Ask the user** which deployment target fits their needs. Each is a valid production choice with different trade-offs.
60
59
60
+
All three targets are container-based, so any language works.
61
+
61
62
> **Product name mapping:** "Agent Engine" / "Vertex AI Agent Engine" is now **Agent Runtime**. Use `--deployment-target agent_runtime`.
62
63
63
64
> **Ambient / scheduled / event-driven agents:** ADK's `trigger_sources` registers `/apps/{app}/trigger/*` endpoints on the same FastAPI app for **all** targets. On **Cloud Run** / **GKE** these are public HTTP routes you point a Pub/Sub push subscription or Eventarc trigger at; on **Agent Runtime** the same routes are reachable through the Agent Engine `/api` passthrough (e.g. `.../reasoningEngines/v1/{resource}/api/apps/{app}/trigger/pubsub`). Cloud Run remains the simplest target for unauthenticated trigger sources. See `/google-agents-cli-adk-code` (`references/adk-python.md`, section "12. Event-Driven / Ambient Agents") for the `trigger_sources` pattern.
@@ -359,6 +360,31 @@ For registering deployed agents with Gemini Enterprise, see `/google-agents-cli-
> **Note:** There are no `agents-cli` commands for these yet. Deploy your agent as usual
366
+
> with `agents-cli deploy`, then configure Agent Gateway and Semantic Governance separately
367
+
> (via Terraform or the Cloud Console).
368
+
369
+
**Agent Gateway** is the networking + security entry/exit point for all agent interactions
370
+
(user↔agent, agent↔tool, agent↔agent) — it centralizes access control and governed
371
+
connectivity (ingress/egress). It is not a deployment target. Deploy your agent with
372
+
`agents-cli deploy`, then attach it to a gateway one of two ways:
373
+
374
+
-**Add the existing agent to a gateway** via the Console / docs flow — see [Route Agent Runtime traffic through Agent Gateway](https://docs.cloud.google.com/gemini-enterprise-agent-platform/scale/runtime/agent-gateway-runtime-deploy) ("For existing agents").
375
+
-**Manage the gateway in Terraform** with [`google_network_services_agent_gateway`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/network_services_agent_gateway) (currently in the `google-beta` provider) — recommended for production, so `agents-cli deploy` owns the agent version and CI/CD handles updates.
Copy file name to clipboardExpand all lines: skills/google-agents-cli-eval/references/metrics-guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Custom metrics are declared in `eval_config.yaml` (or `.json`) under `custom_met
44
44
45
45
Code-based metrics default to **local in-process execution** (no GCP project or region required); opt into the Vertex AI sandbox with `execution: "remote"`.
46
46
47
-
> **Scaffolded default metric.** The scaffolded `eval_config.yaml` ships `custom_response_quality` as a local LLM-judge in `tests/eval/metrics.py` (referenced via `custom_function_file`, run in-process via `google-genai`). It grades on either backend — `genai.Client()` uses `GEMINI_API_KEY` (AI Studio) or ADC (Vertex) — and reads each case's `reference` (ground truth) when present. To grade with the managed Vertex eval service instead, replace it with a built-in metric or an `LLMMetric` (`prompt_template`).
47
+
> **Scaffolded default metric.** The scaffolded `eval_config.yaml` ships `custom_response_quality` as a local LLM-judge in `tests/eval/response_quality.py` (referenced via `custom_function_file`, run in-process via `google-genai`). It grades on either backend — `genai.Client()` uses `GEMINI_API_KEY` (AI Studio) or ADC (Vertex) — and reads each case's `reference` (ground truth) when present. To grade with the managed Vertex eval service instead, replace it with a built-in metric or an `LLMMetric` (`prompt_template`).
0 commit comments