Google Agents CLI Review: Ship AI Agents from the Command Line
TL;DR: Google's Agents CLI is a young but promising way to build and deploy AI agents on Google Cloud. The deployment path looks tidy, the Gemini ties run deep, and the command-line experience is clean. It only works inside Google Cloud, which is both the appeal and the catch.
Google quietly shipped a tool in April 2026 that says a lot about where the cloud giants think AI is heading: not toward chatbots you talk to, but toward agents you deploy like any other piece of software (InfoQ). The Agents CLI is a command-line tool that turns a coding assistant into something that can scaffold, evaluate, and push an AI agent straight onto Google Cloud.
For a business team, the pitch is simple. Instead of stitching together model APIs, hosting, and monitoring by hand, you describe the agent, run a few commands, and Google handles the plumbing. The latest release, v0.5.0, landed on 15 June 2026 (release notes), so this is early software, not a finished product.
That early-stage status matters. A few of the specifics floating around in early write-ups, including ours below, do not line up with Google's own documentation, so treat the command examples as illustrative rather than gospel. We have flagged the gaps where they appear. The bigger story holds up though: Google now has a real, free, open-source path for getting agents into production on its cloud, and the developer experience is the part it clearly sweated over.
What Is Google Agents CLI?
Google Agents CLI is a command-line tool for building and deploying AI agents on Google Cloud:
- Agent definition, reportedly YAML-based agent configuration (Google's docs lead with the Agent Development Kit and a scaffolding flow, and do not confirm a YAML format)
- Gemini integration, built to run Gemini through Google's platform; early coverage cited Gemini 2.0 Pro, but the Agent Platform now runs Gemini 2.5 Pro and the CLI itself stays model-agnostic via the ADK
- Vertex AI, deploy to Google's ML platform
- Cloud Run and GKE, documented runtimes for execution
- Monitoring, observability through Google Cloud
- CLI workflow, the documented commands are
create,enhance,upgrade,install, andplayground
Price: The CLI is open source and free; you pay for the GCP resources your agent uses (GitHub). No official source spells out the pricing in exactly those words, but that is the practical shape of it.
Getting Started
gagents init my-agent --template chat
cd my-agent
gagents test "What's the weather in London?"
gagents deploy --region us-central1A note of caution on the commands above: they reflect an early reviewer build and do not match Google's published docs. The real tool installs via uvx google-agents-cli setup or pipx install google-agents-cli, the command is agents-cli (not gagents), and the documented templates are adk, adk_a2a, and agentic_rag rather than a chat template. Check the Getting Started guide for current syntax before you rely on any of this.
That said, the experience the CLI is going for is clear: get from nothing to a deployed agent in a few minutes, with readable error messages and sensible prompts along the way.
GCP Integration
The CLI leans hard on Google Cloud services. Deployment to Cloud Run, GKE, and Vertex AI reasoning engines is documented; the rest of the table below reflects early-review claims that Google's own docs do not fully confirm, so read the document-storage, BigQuery, and Cloud Monitoring rows as plausible rather than verified.
| Service | Integration | Use Case |
|---|---|---|
| Gemini 2.0 Pro | Native | LLM backend |
| Vertex AI | Deploy target | Model serving |
| Cloud Functions | Runtime | Serverless execution |
| Cloud Storage | Built-in | Document storage |
| BigQuery | Connector | Data analytics |
| Cloud Monitoring | Built-in | Observability |
Deployment Experience
The deploy step is meant to be a single command:
gagents deploy --region us-central1 --memory 2GiGoing by the early-review account, the CLI then:
- Packages agent code
- Creates a serverless deployment
- Configures Gemini access
- Sets up monitoring
- Returns an HTTPS endpoint
One correction here: that account describes deployment to Cloud Functions, but Google's deployment docs list Agent Runtime, Cloud Run, GKE, and Vertex AI reasoning engines as the actual targets. Cloud Functions is not one of them.
Cold start: reported at 2-3 seconds, though this is an unverified reviewer estimate with no published benchmark behind it. Treat it as a rough impression, not a measurement.
Pros and Cons
| Pros | Cons |
|---|---|
| Excellent CLI experience | GCP-only (vendor lock-in) |
| Deep Gemini integration | Limited model choice |
| Fast deployment | Early stage, features missing |
| Good observability | Requires GCP knowledge |
| Serverless scaling | Costs can surprise at scale |
Verdict
Score: 7.9/10 (our subjective rating, not an external benchmark)
Agents CLI is a credible first step from Google. The command-line experience is clean, deployment is quick, and the GCP ties run deep. The flip side is that it is early-stage software and locked to Google Cloud. If your team already lives on Google Cloud, this is a natural fit worth trialling. If you are multi-cloud or sitting on AWS or Azure, hold off for now and watch how it matures.
One more thing for anyone evaluating it seriously: go straight to Google's Getting Started and deployment docs for the current command syntax and supported targets, because the tool is moving fast and a fair bit of the early third-party coverage (ours included) got the specifics wrong.
*Published June 24, 2026 | Google Agents CLI v0.5 (released 15 June 2026)*