agents-cli

The CLI and skills for building agents on Gemini Enterprise Agent Platform.

Get Started   |   Skills   |   Commands   |   PyPI   |   Issues   |   Docs   |   Release Notes   |   Star us

Turn your favorite coding assistant into an expert at building and deploying agents on Google Cloud.

Agents CLI in Agent Platform (agents-cli) gives your coding agent the skills and commands to build, scale, govern, and optimize enterprise-grade agents — so you don't have to learn every CLI and service yourself.

Works seamlessly with: Antigravity CLI  •  Claude Code  •  Codex  •  and any other coding agent.

Get Started

Prerequisites: Python 3.11+, uv, and Node.js.

1. Install

uvx google-agents-cli setup

npx skills add google/agents-cli

2. Open your coding agent

Launch Antigravity CLI, Claude Code, Codex, or any coding agent you prefer.

3. Build your first agent

Ask your coding agent to build something — e.g. "Use agents-cli to build a caveman-style agent that compresses verbose text into terse, technical grunts"

See the full tutorial for a step-by-step walkthrough.

Browse the full documentation →

Agent Skills

CLI Commands

How it works

Architecture

The Google Cloud agent stack that agents-cli builds on:

FAQ

Is this an alternative to Antigravity CLI, Claude Code, or Codex?
No. agents-cli is a tool for coding agents, not a coding agent itself. It provides the CLI commands and skills that make your coding agent better at building, evaluating, and deploying ADK agents on Google Cloud.

How is this different from just using adk directly?
ADK is an agent framework. agents-cli gives your coding agent the skills and tools to build, evaluate, and deploy ADK agents end-to-end.

Do I need Google Cloud?
For local development (create, run, eval), no — you can use an AI Studio API key to run Gemini with ADK locally. For deployment and cloud features, yes.

Can I use this with an existing agent project?
Yes. agents-cli scaffold enhance adds deployment and CI/CD to existing projects.

Can I use agents-cli without a coding agent?
Yes. The CLI works standalone — you can run agents-cli scaffold, eval, deploy, and every other command directly from your terminal. The skills just make it easier for coding agents to do it for you.

How can I extend agents-cli with other skills?
agents-cli skills cover the agent-building lifecycle (scaffold, ADK code patterns, evals, deploy, publish, observability). For adjacent concerns, you could install another skill suite alongside. For example, agent-skills covers general software-engineering workflows (ideation, spec gates, planning, code review), and google/skills covers Google Cloud foundations (BigQuery, Cloud Run, Firebase, GKE).

Feedback

We value your input — it helps us improve agents-cli for the community.

• Bugs & feature requests: open an issue — 👍 the ones you want prioritized
• Share what you built: we'd love to hear about your projects! Reach out at agents-cli@google.com to share your agent or provide feedback

Contributing

The best way to contribute is through feedback: bug reports, feature requests, and ideas shared via issues to directly shape our roadmap.

See the contributing guide for details.

Telemetry

By default, agents-cli emits a single usage signal per command invocation to help improve the tool and better understand how it's used. Each signal is a structured log entry written to your own Google Cloud project: GOOGLE_CLOUD_PROJECT, or else the default project of your Application Default Credentials (logName=projects/<project>/logs/agents-cli), where you can query it in Cloud Logging. It records only the metadata such as command name (e.g. deploy, scaffold.create), exit code, error class, duration (measured from command dispatch to exit, so it excludes CLI startup), CLI/Python versions, and OS — never file contents, arguments, or other input. Commands added by extensions are recorded without their names.

The request that writes the entry also carries usage metadata in its User-Agent and X-Goog-Api-Client headers, which Google receives for agents-cli usage analytics: the CLI and Python versions, the OS and its release, the CPU architecture, the command name and a random per-invocation ID. The log entry's contents, such as the exit code, error class and duration, stay in your project.

To opt out of sending telemetry, use one of the following environment variables:

# our cli-specific variable
# 0, false, no, or off (case-insensitive):
export AGENTS_CLI_TELEMETRY=0

# donottrack.sh standard variable
export DO_NOT_TRACK=1

Use agents-cli info to see the current telemetry state.

Terms of Service

agents-cli leverages Google Cloud APIs. When you deploy agents, you'll be deploying resources in your own Google Cloud project and will be responsible for those resources. Please review the Google Cloud Service Terms for details.