Platform LaunchLatest CLI: v1.4.11Google I/O 2026

Antigravity CLI Deep Dive

Google replaced Gemini CLI with a brand-new, Go-based Antigravity CLI on May 19, 2026. Here is the full developer-level breakdown: what it is, how the four-surface platform fits together, how it auths over SSH, what migrates cleanly, and what does not — all sourced from the official Google announcements and docs.

Editorial illustration of the Antigravity CLI: a dark terminal window with glowing Go gopher motif, agent silhouettes, and connection lines to a separate desktop application window representing Antigravity 2.0.
Antigravity CLI is the terminal surface of a four-product platform that also includes Antigravity 2.0, the Antigravity SDK, and the Antigravity IDE.

On May 19, 2026 at Google I/O, the team behind Gemini CLI announced it was being transitioned into a new product: Antigravity CLI. The rewrite is in Go, the design target is keyboard-first remote work, and the agent backing it is the same harness that powers the Antigravity 2.0 desktop app. At launch (historical, May 2026), Gemini CLI users on a Google AI Pro or Ultra account were given roughly thirty days to switch before requests stopped serving on June 18, 2026. That date has now passed, and the current CLI release is v1.4.11 (checked October 30, 2026).

Transitioning Gemini CLI users to Antigravity CLI We are unifying our efforts around a single harness and platform, Google Antigravity with four distinct surfaces: • Antigravity 2.0 • Antigravity CLI • Antigravity SDK • Antigravity IDE This will allow us to move faster and

— @geminicli May 19, 2026
@geminicli · May 19, 2026

Transitioning Gemini CLI users to Antigravity CLI

The official @geminicli account announcing the unification of Google's developer agent stack into a single platform with four surfaces — Antigravity 2.0, Antigravity CLI, Antigravity SDK, and Antigravity IDE.

Short Answer: What Is Antigravity CLI and How Do I Install It?

Antigravity CLI is Google's terminal agent, and its command is agy. It replaced Gemini CLI for individual users and runs the same agent harness as the Antigravity desktop app. The latest CLI release in the official changelog is v1.4.11 (checked October 30, 2026).

  1. Install: curl -fsSL https://antigravity.google/cli/install.sh | bash (macOS, Linux) or irm https://antigravity.google/cli/install.ps1 | iex (Windows PowerShell).
  2. Check it: agy --version.
  3. Run agy in your project folder and sign in with Google.
  4. Type / for slash commands or /mcp to add MCP servers.
  5. Update: re-run the install command, or brew upgrade --cask antigravity-cli if you used Homebrew.

Get the latest on AI, LLMs & developer tools

New MCP servers, model updates, and guides like this one — delivered weekly.

1. The Announcement

The tweet above came from the team that ships the official Google CLI for Gemini. It does not announce a feature update. It announces a product replacement. The post-by-post sequence on May 19 was: a Google Developers Blog post titled “An important update: Transitioning Gemini CLI to Antigravity CLI”, a launch blog at antigravity.google for Antigravity CLI, a launch blog for Antigravity 2.0, and a public GitHub repository at github.com/google-antigravity/antigravity-cli.

Read together, the framing is unambiguous: Google has decided that “Gemini CLI” as a product name is over, and the entire developer-agent surface area is being unified under the Antigravity brand. The CLI is one of four product surfaces; the other three are Antigravity 2.0 (desktop GUI), Antigravity SDK (programmatic), and the Antigravity IDE (still shipping for now).

2. TL;DR

  • Product: Antigravity CLI — a Terminal UI agent client
  • Replaces: Gemini CLI (for individual-tier users)
  • Language: Go (Gemini CLI was Node)
  • Shared harness: same agent engine as Antigravity 2.0
  • Installs: macOS, Linux, Windows (curl, PowerShell, or CMD)
  • Auth: system keyring with Google Sign-In fallback; SSH-aware
  • Supports: plugins, agent skills, MCP servers, hooks, subagents
  • Async: the CLI orchestrates parallel background subagents
  • Source: public repo at google-antigravity/antigravity-cli
  • Migration: agy plugin import gemini converts extensions to plugins
  • Gemini CLI sunset: June 18, 2026 for individual-tier accounts
  • Enterprise carveout: Gemini CLI continues for Code Assist Standard/Enterprise and paid API keys
Why this matters

If your workflow lives in Gemini CLI today, you are not getting an update. You are getting a parallel product that you have to install, point at your existing config, and validate. Most of your skills, MCP servers, and hooks move over, but the file layout is different, the binary is different, and the command surface has been rebuilt. Treat this as a migration, not an upgrade. For a step-by-step migration walkthrough see our Gemini CLI → Antigravity CLI migration guide.

3. What Antigravity CLI Is

Per the official overview page: Antigravity CLI is the lightweight Terminal User Interface (TUI) surface of Antigravity. It brings the same core agentic capabilities as Antigravity 2.0 — multi-step reasoning, multi-file editing, tool calling, and conversation history — directly to your terminal.

The Google AI Developers account shipped a demo clip of the same product the same day, with the positioning compressed to one sentence:

For those who prefer the terminal, the @Antigravity CLI is lightweight and lets you interact with your agents straight from the command line.

— @googleaidevs May 19, 2026
@googleaidevs · May 19, 2026

Antigravity CLI demo — the terminal surface

For those who prefer the terminal, the @Antigravity CLI is lightweight and lets you interact with your agents straight from the command line.

Concretely, that means three things:

  • It is a TUI, not a GUI. Antigravity CLI is meant to be driven from a terminal, not pointed at by a mouse. The README is explicit that it is “optimized for keyboard-driven workflows and remote SSH sessions with minimal resource overhead.”
  • It shares an agent engine with Antigravity 2.0. The CLI is not running a separate model or a slimmer agent. It is running the same core agent harness as the desktop application, just with a different presentation layer.
  • It is positioned for parallel use with 2.0. You can export a CLI conversation into Antigravity 2.0 to continue working with a richer GUI. Settings and permissions sync bidirectionally.

4. The Four-Surface Platform

Until this week, “Antigravity” meant an IDE. After May 19, 2026, it means a platform with four surfaces, all backed by the same core agent harness. Google DeepMind framed three of the four in a single tweet that same morning:

We’ve created new easy ways to interact with Antigravity: 💻 2.0: A mission control where agents can work together simultaneously on a project ⌨️ CLI: A terminal interface to work with agents ⚙️ SDK: A toolkit that lets your software automatically connect to and use our AI

— @GoogleDeepMind May 19, 2026
@GoogleDeepMind · May 19, 2026

The Antigravity surfaces — DeepMind's framing

2.0: A mission control where agents can work together simultaneously on a project. CLI: A terminal interface to work with agents. SDK: A toolkit that lets your software automatically connect to and use our AI agents.

Adding the original Antigravity IDE, here is the full four-surface picture:

  • Antigravity 2.0 — new standalone desktop app for macOS, Linux, and Windows. Agent-first, no IDE. Includes dynamic subagents, async task management, JSON hooks, and Scheduled Tasks (cron-style invocation). See our Gemini 3.5 Flash developer guide for the model context around 2.0.
  • Antigravity CLI — the subject of this post. Terminal-first agent surface, rebuilt in Go.
  • Antigravity SDK — programmatic surface for embedding the harness into your own apps. Announced alongside 2.0 and the CLI.
  • Antigravity IDE — the original product. Still shipping, but the Agent Manager surface inside it is being deprecated in favor of the standalone 2.0 app in a future release.

The reason this matters for the CLI specifically: improvements to the core harness ship to every surface at once. A new tool the agent can call, a better planning loop, a new permission model — you do not wait for the CLI team to backport.

5. CLI vs Antigravity 2.0

Same engine, different ergonomics. The official feature table:

FeatureAntigravity CLIAntigravity 2.0
Primary focusSpeed, keyboard efficiency, low overheadComprehensiveness, visual orchestration
InterfaceTerminal User Interface (TUI)Full GUI desktop application
WorkflowSSH / remote sessions, keyboard-firstLocal workspace, heavy orchestration
Agent engineShared core agent engineShared core agent engine

Practical reading: the CLI is what you reach for when you are on a remote box, on a slow connection, in a tmux pane, or just allergic to GUIs. The 2.0 desktop app is what you reach for when you want artefact previews, the visual review flow on diffs, voice input, and the Scheduled Tasks dashboard.

6. Installation: How to Install Antigravity CLI (Windows, Mac, Linux)

PlatformCommand
macOScurl -fsSL https://antigravity.google/cli/install.sh | bash
Linux (and Googlebook Linux Terminal)curl -fsSL https://antigravity.google/cli/install.sh | bash
Windows PowerShellirm https://antigravity.google/cli/install.ps1 | iex
Windows CMDcurl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd
Homebrew (macOS, Linux)brew install --cask antigravity-cli
  1. Run the command for your platform in a terminal.
  2. Open a new terminal window so the updated PATH is picked up.
  3. Run agy --version to confirm the install.
  4. Run agy inside a project folder to start the first-run sign-in (see section 7).

The Homebrew cask is listed on formulae.brew.sh as antigravity-cli at version 1.4.11, links its binary as agy, requires macOS 12 or later, and is flagged auto_updates. It lives in homebrew/cask and is not shown on Google's install page, so treat the script as the primary route. Google's install page lists the CLI as v1.4.4, while the changelog and cask list v1.4.11, so trust agy --version after installing.

Installer flags (official): --skip-aliases stops the script from purging or updating legacy agy or antigravity shell aliases, and --skip-path stops it from editing your shell profile PATH. Install location (official troubleshooting docs): the binary goes to ~/.local/bin on macOS and Linux, or C:\Users\<you>\AppData\Local\agy\bin on Windows. If agy is not found afterwards, that folder is not on your PATH.

Original May 2026 install notes (kept for context):

The README publishes three install commands. They are all one-liners that pull a shell script from antigravity.google/cli/install.*:

# macOS / Linux
curl -fsSL https://antigravity.google/cli/install.sh | bash

# Windows PowerShell
irm https://antigravity.google/cli/install.ps1 | iex

# Windows CMD
curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd

After install, the binary is agy (not antigravity — important when scripting). Verify with agy --version. Antigravity CLI is also dual-distributed: the same project is published as a public Go repository at github.com/google-antigravity/antigravity-cli with a demo GIF and a links table pointing at the official docs.

Trust step

curl | bash is the canonical install path, which is fine for an official Google domain but worth treating as a trust step. Inspect the script before piping it on shared infrastructure: curl -fsSL https://antigravity.google/cli/install.sh -o /tmp/agy-install.sh && less /tmp/agy-install.sh.

7. Auth, Including Remote SSH

The CLI auths via the system keyring with a Google Sign-In fallback. Two flows worth knowing:

  • Local: first run opens your default browser. Sign in with a Google account associated with Google AI Pro, Ultra, Gemini Code Assist, or an enterprise GCP project. The credential is stored in the system keyring.
  • Remote / SSH: the CLI detects an SSH session and instead prints an authorization URL. You open the URL on your local machine, complete the OAuth flow, and the token gets pinned back to the SSH session. This was a notable pain point in early Gemini CLI flows; it is now a first-class case.
  • Sign out: /logout clears saved credentials.

For enterprise access, you connect a GCP project during onboarding. The CLI then routes calls through that project for billing and quota. The official enterprise page covers the GCP project requirements; the consumer flow does not need one.

8. The Shared Agent Harness

This is the architectural decision that explains every other choice in the product. Both Antigravity CLI and Antigravity 2.0 run on the same core agent engine. From the official CLI blog post:

“A primary goal for the Antigravity CLI was the consolidation of a single agent harness across Google-built developer surfaces for more rapid future improvements.”

Three implications:

  • Settings and permissions sync bidirectionally. A model permission set in 2.0 applies in the CLI, and vice versa. You do not maintain two allowlists.
  • Conversations export sideways. Conversations are not shared across products by default, but you can pull a CLI conversation up in 2.0 via the @conversation dropdown to continue with the GUI.
  • Improvements ship once. When Google ships a better tool-routing algorithm or a smarter planning loop into the harness, both surfaces get it on the same day. No CLI-team backport.

9. Context Files and Rules

Antigravity CLI reads the same context files Gemini CLI did:

  • Workspace context: GEMINI.md and AGENTS.md from the active workspace directory.
  • Global context: ~/.gemini/GEMINI.md, automatically loaded and enforced across all workspaces.

If you have rules files for the existing Gemini CLI flow, they keep working. For a structured cross-tool rules pattern, see our AGENTS.md guide and GEMINI.md system prompt guide.

10. Plugins (was: Extensions)

Gemini CLI shipped extensions as the package format for sharing capabilities. Antigravity CLI renames this surface to plugins— per the official docs, “the industry has standardized on the term”.

On first launch you get a migration prompt that converts Gemini CLI extensions to Antigravity plugins. If you skip it or install the CLI elsewhere, run the import explicitly:

agy plugin import gemini

Real output from the official docs, showing the import walking a multi-component extension:

[ok]    conductor
          - skills      : skipped (not found)
          - agents      : skipped (not found)
          ✔ commands    : 6 processed (converted to skills)
          - mcpServers  : skipped (not found)
          - hooks       : skipped (not found)
[ok]    google-workspace
          ✔ skills      : 6 processed
          - agents      : skipped (not found)
          ✔ commands    : 4 processed (converted to skills)
          ✔ mcpServers  : 1 processed
          - hooks       : skipped (not found)

Things to know: custom themes do not migrate; commands become skills (the older commands concept gets folded into the broader skills primitive); MCP servers move over but the config file location changes (see section 12).

11. Agent Skills

Agent skills are the smallest unit of reusable agent behavior — small files describing a slash command and what the agent should do when invoked. They came out of Gemini CLI and remain a first-class concept in Antigravity CLI, managed with the same /skills command.

Locations changed:

ScopeGemini CLIAntigravity CLI
Global~/.gemini/skills/~/.gemini/antigravity-cli/skills/
Workspace.gemini/skills/ or .agents/skills/.agents/skills/

Global skills are picked up automatically, no action needed. Workspace skills in the older .gemini/skills/ folder need to be moved to .agents/skills/. For a deeper walkthrough on writing skills, see our Antigravity skills setup guide and mastering agent skills.

One missing piece worth flagging: Antigravity CLI does not yet have an equivalent of the gemini skills command for managing skills from the terminal. You either author skill files by hand or install via npx skills install.

12. MCP Servers

Antigravity CLI supports both local and remote MCP servers via the same /mcp command. Two config differences from Gemini CLI to watch for:

  • Separate config file. Antigravity stores MCP server config in a dedicated mcp_config.json file, not inline in settings.json. Global: ~/.gemini/config/mcp_config.json per Google's current MCP docs (the May 2026 version of this page listed ~/.gemini/antigravity-cli/mcp_config.json, which was the earlier location; a changelog entry mentions a migration to the config/ path). Workspace: .agents/mcp_config.json.
  • Field rename. For remote MCP servers, Antigravity CLI uses serverUrl instead of url (or the deprecated httpUrl). A copied-over Gemini CLI config will fail silently on remote servers if you do not rename the field. Update (October 2026): the docs still say url and httpUrl are unsupported, while one changelog entry says the schema now also accepts url, so keep using serverUrl to be safe.
  • CLI management. The /mcp panel enables, disables and inspects servers, and the CLI changelog notes that the panel keeps fields it does not recognize (enabledTools, timeoutSeconds,tools.eager) when you toggle a server. I found no documented agy mcpshell subcommand, so edit the JSON file for scripted setups.

For background on MCP configuration patterns, see our MCP tutorial and the custom MCP server guide.

13. Hooks and Subagents

Both features carry over from Gemini CLI and the Antigravity 2.0 lineage:

  • Hooks. Defined as JSON. They let you intercept and control the agent at specific lifecycle moments — before a tool call, after a file edit, on session start. This is the same JSON hook format introduced in Antigravity 2.0.
  • Dynamic subagents. The main agent can spawn focused subagents for parallel work. This is how the CLI advertises async / background workflows: big refactors and multi-topic research that used to lock up a terminal session now run as subagents while you keep typing.

For the multi-agent pattern in practice, see our multi-agent orchestration walkthrough.

Antigravity CLI Commands (agy command reference)

Added October 30, 2026, checked against Google's CLI reference and CLI v1.4.11. The executable is agy. Run it bare to open the terminal UI, or pass flags to change the session. These are the flags in Google's CLI reference:

Command or flagWhat it does
agyOpens the interactive terminal UI in the current folder.
agy -p "prompt"Runs one prompt non-interactively (headless print mode). Aliases: --print, --prompt.
-i, --prompt-interactiveRuns an initial prompt interactively, then continues the session.
-c, --continueContinues the most recent conversation.
--conversation <id>Resumes a previous conversation by ID.
--modeSets the execution mode: accept-edits, auto (Preview) or plan.
--model, --effort, --agentPick the model, reasoning effort and agent for the session. List them with agy models and agy agents.
--add-dirAdds a directory to the workspace. Repeatable.
--output-formatPrint-mode output: text, json or stream-json.
--json-schemaEnforces structured output in print mode.
--sandboxTurns the terminal sandbox on for this session.
--dangerously-skip-permissionsAuto-approves every tool permission request. Use with care.
--remote-controlStarts a Remote Control connection for the session.
agy plugin install | list | validateManages plugins from the shell (see the plugins section above).

I did not find an agy update, agy uninstall or agy mcp subcommand in Google's documentation, so this page does not list them. Some older guides call the command antigravity; the command you type is agy.

Antigravity CLI Slash Commands

Type / in the prompt box to browse commands, and press Tab to accept the highlighted autofill. The documented list at the time of this update:

Slash commandPurpose
/configInteractive settings editor (alias /settings).
/model, /effortChoose the model and the reasoning effort.
/mcpOpen the MCP server manager.
/pluginPlugins manager, or inline install, uninstall, enable, disable, list (alias /plugins).
/skillsBrowse loaded skills. /skills reload re-reads them from disk.
/permissionsManage allow, ask and deny rules for tools.
/hooksBrowse active hooks.
/agents, /tasksManage custom agents and background subagents; monitor background shell tasks.
/plan, /goal, /boost, /teamworkPlanning and deeper reasoning workflows (/teamwork is for paid plans).
/resume, /fork, /rewind, /rename, /clearConversation management: resume, branch, roll back, rename, reset.
/diff, /context, /usage, /creditsReview changes, view context use, check quota and credits.
/add-dir, /open, /copy, /btwAdd a workspace folder, open a path in your editor, copy a response, ask a side question.
/remote-control, /schedule, /voiceRemote Control toggle, timers and cron schedules, and voice dictation.
/logoutDisconnects your account and clears saved tokens from the OS keyring.
/help, /changelog, /feedback, /exitHelp panel, release notes, feedback, and quit (alias /quit).

This list is a condensed version of the full reference table, which also includes /artifact, /browser, /codesearch, /grill-me, /keybindings, /learn, /statusline and /title. The list changes between releases, so run /help for the set your version ships.

Antigravity CLI Modes and Auto Mode

Press Shift+Tab in the prompt box to cycle modes in this order: default, accept-edits, auto, plan. Start in a specific mode with agy --mode=accept-edits, agy --mode=auto or agy --mode=plan, or save a default with agentMode in settings.json.

ModeBehavior
defaultShows a diff for review before file edits and asks before terminal commands.
accept-editsAuto-approves file creations and edits inside the workspace. Still asks before terminal commands.
auto (Preview)Auto-approves edits, runs commands inside the terminal sandbox, and checks commands that need to leave the sandbox so safe, reversible ones run without a prompt.
planResearches with read-only tools and presents a plan for your approval before any edit.
  1. Make sure the terminal sandbox is available (macOS and Linux, or Windows 11 24H2 or later with the August 2026 update).
  2. Run agy --mode=auto, or set "agentMode": "auto" in ~/.gemini/antigravity-cli/settings.json.
  3. Check the bottom-right status bar. It shows auto when the mode is active.

Auto mode needs CLI v1.3.5 or later on macOS and Linux and v1.4.4 or later on Windows. It is not available for business or enterprise accounts. Where it is unavailable the CLI starts in default mode and auto is left out of the Shift+Tab cycle. Settings such as toolPermission: "strict" or always-proceed override auto mode. For a longer walkthrough, see our auto-accept and autopilot guide.

Antigravity CLI settings.json

The user settings file is ~/.gemini/antigravity-cli/settings.json. Edit it by hand or through /config. A key you leave out uses its default. Add "$schema": "https://antigravity.google/schemas/v1/settings.json" at the top for editor autocomplete.

KeyDefaultNotes
agentMode"" (default)"accept-edits", "auto" or "plan".
toolPermissionrequest-reviewAlso proceed-in-sandbox, always-proceed and strict.
enableTerminalSandboxfalseRuns agent commands inside the OS sandbox.
allowNonWorkspaceAccessfalseLets the agent touch files outside the workspace.
modelProvider""Set to gemini to use a GEMINI_API_KEY instead of a Google sign-in.
colorSchemeterminalTheme, for example dark or tokyo night.
notificationsfalseTerminal bell and desktop notification when the agent needs you.
verbositymediumhigh, medium or low.
permissionsnoneObject with allow, ask and deny rules.

Google's reference lists more keys (editor, editorMode, historySize, queuedMessages, sandboxProxy and others). Rules for MCP servers live in a separate mcp_config.json, covered in the MCP section above.

Antigravity CLI vs Gemini CLI: What Changed

Gemini CLIAntigravity CLI
Commandgeminiagy
Config folder~/.gemini~/.gemini/antigravity-cli
MCP configinside settings.jsonseparate mcp_config.json, remote servers use serverUrl
ExtensionsExtensionsPlugins (agy plugin import gemini brings extensions across)
Individual accountsCut off June 18, 2026 (historical)The supported path for Google AI Pro, Ultra and free accounts

Moving over takes a few commands. Our Gemini CLI to Antigravity CLI migration guide walks through them step by step.

How to Update Antigravity CLI

Added October 30, 2026. Google's CLI reference points to its installation page for updating, which I could not load, so I cannot quote an official update command. What the sources do show:

  1. Check your version with agy --version and compare it with the latest release in the official changelog (v1.4.11 on October 30, 2026).
  2. Homebrew installs: run brew upgrade --cask antigravity-cli. The cask is marked as auto-updating.
  3. Script installs: re-running the install command from the installation section is the likely way to get the newest binary. This is my inference, not a documented step. The CLI changelog also mentions automatic plugin updates, which are separate from updating the CLI itself.
  4. Googlebooks: update or reinstall through Google Play.
  5. Run /changelog inside the CLI to read release notes for your installed version.

How to Uninstall Antigravity CLI

Google does not publish an uninstall command. The steps below combine Google's documented install paths and the Homebrew cask definition. Our uninstall Antigravity guide covers the desktop app; it does not cover the CLI.

  1. Run /logout inside the CLI to clear saved tokens from your OS keyring.
  2. Homebrew: brew uninstall --cask antigravity-cli. Add --zap to also trash ~/.gemini/antigravity-cli.
  3. Script install on macOS or Linux: delete the agy binary in ~/.local/bin.
  4. Script install on Windows: delete the agy binary in %LOCALAPPDATA%\agy\bin.
  5. Remove the PATH line the installer added to your shell profile, unless you installed with --skip-path.
  6. Optional: delete ~/.gemini/antigravity-cli for settings and ~/.gemini/config for shared rules, skills, hooks and MCP config. Deleting the second folder also affects other Antigravity surfaces that share it, so check first.

If agy fails to start rather than install, see our agy CLI errors troubleshooting guide.

14. The Security Footnote

The README ships a warning block. It is short and worth quoting in full:

“AI coding agents are known to have certain security risks, including autonomous code execution, data exfiltration, prompt injection, and supply chain risks. Ensure that you monitor and verify all actions taken by the agent.”

The interactions data Google collects is opt-out-able from settings. The CLI defaults to data collection on consumer tiers. Enterprise behavior follows your GCP project policies. For a fuller treatment of the threat model and the controls worth tuning, see our Antigravity security guide and the dangerous commands prevention guide.

15. What It Is Not (Yet)

Things the official docs explicitly call out as not present in Antigravity CLI at launch:

  • Custom themes don't migrate. Some Gemini CLI extensions include custom themes; those components are dropped during plugin import.
  • No skills CLI command. Skills are still managed inside the agent via /skills, but there is no equivalent of gemini skills for terminal-level management. File authoring or npx skills install is the workaround.
  • No 1:1 feature parity claim. Google explicitly says “there won't be 1:1 feature parity right out of the gate.” The promise is “the most critical features” — skills, hooks, subagents, plugins. If you depended on a specific peripheral Gemini CLI command, check before assuming.

16. Who Antigravity CLI Is For

Install it if
  • You used Gemini CLI on a Google AI Pro / Ultra account — the June 18, 2026 cutoff Google announced has passed (historical note)
  • You live in tmux, on a remote server, or in a terminal-first IDE
  • You want the same agent harness as Antigravity 2.0 but without the GUI
  • You orchestrate background subagents and want them not blocking your shell
  • You want to keep MCP servers, skills, and hooks portable across surfaces
Skip it (for now) if
  • You are on a Code Assist Standard / Enterprise license — Gemini CLI keeps working
  • You rely on a paid Gemini API key — same, Gemini CLI is still supported
  • Your workflow centers on artefact previews, the visual diff review, or voice input — you want 2.0
  • You depend on a Gemini CLI peripheral feature that has not been ported yet — wait a release

17. FAQ

Q: Is Antigravity CLI free?

The CLI itself is free to install and the repository is public on GitHub. Usage is gated by your Google account tier — Google AI Pro, Ultra, or Gemini Code Assist quota for individuals; enterprise plans or paid Gemini API keys for organizations.

Q: Does Antigravity CLI work over SSH?

Yes — explicitly. The CLI detects SSH sessions and prints an authorization URL you complete in a local browser. Remote SSH was a first-class design target, not an afterthought.

Q: What language is Antigravity CLI written in?

Go. Google rebuilt the terminal experience in Go for lower memory overhead and faster startup compared to the Node.js-based Gemini CLI. The shared agent harness behind it is the same engine that powers Antigravity 2.0.

Q: Do my Gemini CLI extensions still work?

Most do. First launch prompts a migration that converts extensions to Antigravity plugins. You can also run agy plugin import gemini manually. Custom themes and a few minor components do not migrate cleanly; skills, commands, MCP servers, and hooks generally do.

Q: Is Antigravity CLI the same as Antigravity 2.0?

No. They share an agent engine and sync settings, but they are different binaries. 2.0 is a desktop GUI focused on visual orchestration. The CLI is a TUI focused on speed and remote workflows.

Q: Can I keep using Gemini CLI?

If you are on Code Assist Standard or Enterprise, or you use a paid Gemini API key, yes — indefinitely. If you are on Google AI Pro, Ultra, or free Gemini Code Assist for individuals, Google said Gemini CLI would stop serving requests on June 18, 2026. That date has now passed, so individual accounts should use Antigravity CLI.

Q: Does Antigravity CLI support MCP servers?

Yes, both local and remote. Configs live in mcp_config.json (not inline in settings.json as Gemini CLI did). Remote servers use the serverUrl field, not url. Google's current docs put the global file at ~/.gemini/config/mcp_config.json and the workspace file at .agents/mcp_config.json.

Q: How do I install Antigravity CLI?

On macOS or Linux run curl -fsSL https://antigravity.google/cli/install.sh | bash. On Windows PowerShell run irm https://antigravity.google/cli/install.ps1 | iex. Windows CMD has its own install.cmd one-liner, listed in the installation section. Confirm with agy --version.

Q: What is the agy command?

agy is the executable for Antigravity CLI. Run it to open the terminal UI, or use agy -p "prompt" for a single headless prompt. Documented subcommands include agy plugin, agy models and agy agents.

Q: How do I log in to Antigravity CLI?

Run agy. It signs in silently from your OS keyring if a saved session exists, otherwise it opens your browser. Over SSH it prints a URL and asks you to paste back an authorization code. /logout clears the saved session. For headless use, set modelProvider to gemini and export GEMINI_API_KEY.

Q: How do I update Antigravity CLI?

Google's docs I could load do not document an agy update command. Homebrew users can run brew upgrade --cask antigravity-cli; script installs can most likely be refreshed by re-running the install command (my inference). Latest release in the official changelog: v1.4.11.

Q: How do I uninstall Antigravity CLI?

There is no documented uninstall command. Run /logout, then remove the agy binary from ~/.local/bin (or %LOCALAPPDATA%\agy\bin on Windows), or run brew uninstall --cask antigravity-cli for Homebrew installs. Full steps are in the uninstall section above.

Q: What is auto mode in Antigravity CLI?

A Preview execution mode that auto-approves edits, runs commands in the terminal sandbox, and checks commands that need to leave it. Start it with agy --mode=auto. It is not available for business or enterprise accounts.

18. Verdict

Our Take

Antigravity CLI is the better daily driver if you used Gemini CLI on a consumer-tier Google account (written in May 2026, before the June 18, 2026 cutoff; that date has now passed). The Go rewrite is real (startup is fast, memory is low), SSH is a first-class flow, the plugin migration is one command, and you stop running a parallel agent to whatever lives in your desktop app. The reasons to hold off are narrow: enterprise license, paid API key, or one specific Gemini CLI feature you can prove has not shipped yet.

If you only do one thing this week: install Antigravity CLI on the machine where you used Gemini CLI most, run agy plugin import gemini, and try a twenty-minute task you would normally run in the old CLI. You will know inside a single session whether the migration is going to be smooth.


Related Guides

For the migration step-by-step, see Gemini CLI → Antigravity CLI migration. For the model that powers all four surfaces, see the Gemini 3.5 Flash developer guide. For older Gemini CLI workflows that mostly still apply, our Gemini CLI setup guide.


Sources