CLI · Coding agents · Google
Google Antigravity CLI
Work with Google's coding agents from the terminal, with project context, reviewable changes and configurable tools.
Migration carries access decisions. Imported plugins, credentials and MCP settings may preserve broader access than a new task needs. Inspect them before starting agent work.
Understand the tool
What it does.
Antigravity CLI is Google's agy terminal interface to its coding agents. It supports project investigation, changes and parallel agent work. Google directed free and Google AI Pro/Ultra Gemini CLI users to Antigravity in June 2026; the announcement explicitly preserved specified enterprise and paid API-key access to Gemini CLI.
Why use it?
Consider it when you want a terminal workflow within Google's current agent tooling. Start with one project and a small outcome. The permission panel and change viewer help you inspect what the session can access and what it has changed.
A useful fit for
- Google agent workflows
- Reviewing project changes in a terminal
- Evaluating a Gemini CLI migration
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Investigate a small project change
A developer needs to add a validation rule without changing unrelated behavior.
- Open the project and inspect active permissions.
- Ask for the relevant implementation and test plan.
- Review the proposed change and its validation before accepting it.
Intended outputA scoped implementation proposal with a visible review step.
Use case 02
Review a Gemini CLI migration
A team has existing rules, skills and server configuration.
- Inventory the existing configuration before onboarding conversion.
- Use the official migration guide to check skill paths and MCP schema changes.
- Review imported permissions and test each integration separately.
Intended outputA migration checklist that identifies what carried over and what still needs verification.
A concrete starting point
Inspect active permissions inside the CLI
Enter this documented slash command inside an existing agy session. It opens the tool-permissions panel; it is not a command for your operating-system shell.
/permissionsWhat this can change
Displays configuration in the current session. Changing settings in the panel can alter future tool access; simply opening it does not request a code change.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- Antigravity CLI installed for the supported platform
- An eligible personal or business account, or another documented authentication route
- An authorized workspace; review any imported plugins or server definitions
- Authentication
- The CLI supports saved native-keyring sessions and documented sign-in flows. Account eligibility and enterprise controls differ.
- Can read
- Permitted project files
- Context returned by enabled tools and integrations
- Can write or change
- Files and terminal actions permitted by configuration
- Session and migrated configuration state
- Network and data flow
- Google model and authentication services
- Approved browser, MCP and tool endpoints
- Approval and control
- CLI permissions distinguish allowed, denied and approval-required actions. Inspect the CLI-specific rules rather than assuming desktop settings describe every CLI behavior.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Windows, macOS and Linux; consult current platform instructions
- Gemini configuration migration has partial parity and changed paths/schema
Costs and account requirements
Quotas, model access and optional credit overages vary by plan and account. Confirm the CLI's current AI-credit settings before a long task.
Current pricing or plan information ↗Google service terms
Do not infer the current CLI's license from the separately published Apache-licensed Gemini CLI repository. Account-specific terms apply.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
Migration carries access decisions
Imported plugins, credentials and MCP settings may preserve broader access than a new task needs. Inspect them before starting agent work.
Agent output needs review
Generated edits and terminal requests can be wrong. Keep project scope small and inspect changes before running them against real services.
Where it may fall short
- No public source repository for the current CLI binary was verified in this review.
- Gemini CLI's consumer transition is not a statement that every enterprise or API-key use ended.
Observed behavior · 2026-10-18
Runtime and security findings.
The native CLI stored and listed a synthetic HTTP MCP definition without signing in. Gemini-provider startup correctly stopped when its API key was missing. Agent execution was not tested.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation
MCP registration does not establish a working connection
The CLI listed the synthetic http://127.0.0.1:1/mcp server as enabled although no server listened there. The result is configuration state only.
In practice: Test server connectivity and permission scope separately; do not interpret enabled as verified.
Observed in this evaluation
Provider selection changes credential handling
With modelProvider set to gemini in the isolated settings file, a print invocation exited 1 because GEMINI_API_KEY was absent. No account-based sign-in or model request was performed.
In practice: Choose the intended provider explicitly and keep its credentials out of shared settings and logs.
Version, environment and fixture
- Version or deployment
- 1.4.2
- Tested target
- Official Google Antigravity CLI Windows x64 binary
- Artifact identity
- SHA-256 4f6c7a807f3fae54bc61e74b8469ac79d07702ade5c62de62041bba44e2a7be0 of the official downloaded agy.exe artifact. SHA-512 matched the official release manifest; Windows Authenticode returned Valid for Google LLC.
- Environment and fixture
- Windows 11 x64; Python 3.12.10 harness. Raw timestamps UTC.
- Fresh per-tool home/config/cache; child environment constructed from OS/runtime paths, explicit isolation variables and no inherited credentials. Synthetic fixtures only; no user account sign-in.
Checks and results
5 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Downloaded versionMet expectation
- Method
<evaluation>\downloads\cli\agy.exe --version- Expected
- Print the pinned binary version.
- Observed
- Exit 0. 1.4.2
Gemini provider without API keyMet expectation
- Method
Set HOME and USERPROFILE to the empty per-tool fixture home. Write <fixture-home>/.gemini/antigravity-cli/settings.json containing {"modelProvider":"gemini"}; omit GEMINI_API_KEY from the child environment. Command: <evaluation>\downloads\cli\agy.exe --print fixture --print-timeout 5s- Expected
- Stop before sign-in/model execution when modelProvider=gemini and GEMINI_API_KEY is absent.
- Observed
- Exit 1. modelProvider is set to "gemini" in settings.json, but the GEMINI_API_KEY environment variable is not set. Set GEMINI_API_KEY to your Gemini API key, or remove "modelProvider" from settings.json to use the default backend.
Store synthetic HTTP MCP definitionMet expectation
- Method
<evaluation>\downloads\cli\agy.exe mcp add --type http ionbin-fixture http://127.0.0.1:1/mcp- Expected
- Write a localhost-only definition in the isolated configuration.
- Observed
- Exit 0. Added MCP server "ionbin-fixture" (http)
Read synthetic MCP definitionMet expectation
- Method
<evaluation>\downloads\cli\agy.exe mcp list- Expected
- List the stored URL and enabled state.
- Observed
- Exit 0. NAME TYPE STATUS COMMAND/URL ionbin-fixture http enabled http://127.0.0.1:1/mcp
Reject trailing HTTP-server argumentsMet expectation
- Method
<evaluation>\downloads\cli\agy.exe mcp add ionbin-invalid http://127.0.0.1:1/mcp --type http- Expected
- Reject unsupported command arguments on an HTTP MCP definition.
- Observed
- Exit 1. Error: http server type does not accept command arguments
Practical caveats
- The official installer was inspected, then the verified binary was downloaded directly; PATH/profile setup and automatic updates were not tested.
- The normal account path can use the operating-system keyring; this test intentionally selected the key-based provider with no key.
What this evaluation does not establish
- Authenticated model behavior, workspace trust prompts, terminal sandbox enforcement and permission approvals.
- MCP connection/tool execution, prompt injection resistance, keyring storage and background updates.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
An editorial starting point for Google's current consumer coding-agent path. Documented migration and permission details support inclusion; no effectiveness or market-share ranking was measured.
The number is an editorial starting order within the cli tools collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Official CLI commands, authentication, permissions and migration announcement
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- CLI command reference ↗antigravity.google
- Authentication ↗antigravity.google
- Permissions ↗antigravity.google
- Migration guide ↗antigravity.google
- Google's audience-specific transition announcement ↗developers.googleblog.com
- Terms ↗antigravity.google