Google's Agents CLI: Shipping Agents from the Command Line.

Analysis

Most of the noise around AI agents in 2026 has been about what they can do. Less attention has gone to a duller but more useful question: once you have written one, how do you actually get it running, keep it secure, and know when it breaks? That is the gap Google is aiming at with the Agents CLI.

The pitch is simple enough for a non-engineer to follow. Shipping an agent has felt closer to a science project than a deployment: wiring up permissions, secrets, networking, and monitoring by hand. Google's tool tries to fold that work into a single command-line workflow, so the path from "agent code on my laptop" to "agent running on Google Cloud" is shorter and more repeatable.

One caveat worth setting up front. Google describes the Agents CLI as the programmatic backbone for the agent development lifecycle on Google Cloud, and in practice it leans toward a skills layer that turns coding assistants such as Gemini CLI, Claude Code, and Cursor into ADK-savvy helpers (Google Developers Blog). It is reportedly less of a generic "deploy agents the way you deploy containers" toolchain than some early coverage made it sound. Keep that distinction in mind as you read the rest.

The Core Workflow

For anyone used to cloud-native tooling, the shape of the workflow is recognisable: scaffold a project, define what the agent can do, test it locally, deploy it, then watch the logs. The exact command names below come from secondary reporting and do not match Google's documented invocation (the real tool runs as agents-cli and installs via npm or uvx), so read this as the intended flow rather than verbatim syntax:

# Initialise a new agent project
gcloud agents init billing-agent --template=python

# Define skills in skills.yaml
gcloud agents skills add --name="query-database" --type=python

# Test locally
gcloud agents test --input="What was last month's revenue?"

# Deploy to Cloud Run
gcloud agents deploy billing-agent --region=us-central1

# Monitor
gcloud agents logs billing-agent --follow

The Skills Framework

A "skill" here is a modular Python or TypeScript function with a defined shape for its inputs and outputs. The article that this is based on describes each skill living in a skills.yaml manifest, though that format could not be confirmed against Google's docs (the real product reportedly uses an npm-installed skills architecture under an .agents/skills/ path, not a YAML manifest like this):

skills:
  - name: query_database
    description: Execute a read-only SQL query against the analytics database
    handler: src.skills.query:execute
    input_schema:
      type: object
      properties:
        query:
          type: string
          description: The SQL query to execute
      required: [query]
    output_schema:
      type: object
      properties:
        rows:
          type: array
        execution_time_ms:
          type: integer

The idea behind it is straightforward. From a schema like this, the tooling generates client code that matches the types, checks inputs at runtime, and takes care of serialisation, error handling, and retries so you do not have to write that boilerplate yourself. Skills can also call other skills, which lets you build bigger capabilities out of smaller ones.

Integration with Google Cloud

This is where being on Google Cloud pays off. The Agents CLI can deploy to Cloud Run, and also to Agent Runtime and GKE, with the target being configurable rather than fixed (Google Cloud Blog). Cloud Run brings automatic scaling, IAM, and Cloud Monitoring along with it. The tool also handles the service account setup, secret management through Secret Manager, and VPC connectivity. For a business already inside Google's security model, that removes a lot of the authentication and networking plumbing a self-hosted agent would otherwise need.

The commands below are again from secondary reporting and do not appear in Google's documentation, so treat them as illustrative of intent:

# Grant the agent access to BigQuery
gcloud agents permissions add billing-agent   --role=roles/bigquery.dataViewer   --dataset=analytics.revenue

# Connect to a VPC for database access
gcloud agents network attach billing-agent   --vpc-connector=agents-connector

Comparison with Open-Source Alternatives

The Agents CLI sits in a different spot from general-purpose agent frameworks. It is a deployment and packaging tool for single-purpose agents that lean on Google Cloud services, not a framework for building any agent you can imagine. So the useful question is less "which agent framework" and more "where am I deploying."

The table below compares it against three open-source options. A flag worth stating plainly: the competitor products named here (Hermes, OpenClaw, OpenHuman) and their pricing and marketplace details could not be verified against any authoritative source, and may be the original publication's own internal comparison. Read the non-Google rows as unconfirmed.

The Vendor Lock-In Question

The obvious worry is portability. Skills written in Google's format do not drop cleanly into other ecosystems, and an agent deployed to Cloud Run will not move to AWS Lambda or your own servers without rework. If your business is committed to Google Cloud, that trade is fine. If you want the freedom to switch clouds later, it is a real constraint to weigh up now rather than after you have built on it.

When to Use It

The Agents CLI is at its best for single-purpose agents that need to talk to Google Cloud services like BigQuery, Firestore, Pub/Sub, or Vertex AI. Think a revenue reporting agent, a document processing agent, or a customer support triage agent. It is a weaker fit for general coding assistants, multi-channel messaging bots, or desktop companion agents.

The bigger point is what the workflow signals. Define skills, test locally, deploy to managed infrastructure, watch the logs: that loop is starting to look like the default way agents get shipped, whether you use Google's tool or not. For Australian teams already on Google Cloud, it is worth a look. For everyone else, it is a preview of where agent deployment is heading.