Antigravity CLI

Gemini CLI is being merged into Antigravity CLI. For unpaid tier and Google One users, the transition happens on June 18, 2026. For enterprise users, Gemini CLI continues alongside the new Antigravity CLI. This lesson covers the Antigravity CLI: what it is, how it differs from Gemini CLI, and what the migration means for your workflows.

What you'll learn

• Antigravity CLI is the lightweight, terminal-first surface for the Antigravity platform
• It runs autonomous coding agents, executes shell commands, and manages background subagents from the keyboard
• Gemini CLI skills, GEMINI.md context files, and MCP servers transfer directly to Antigravity CLI

The problem

You have been using Gemini CLI for months. You have custom slash commands, MCP servers connected, and a GEMINI.md file that shapes how the agent works. Google announces that Gemini CLI is being replaced by Antigravity CLI. You need to know what changes, what stays the same, and whether you need to rewrite your configuration.

The short answer: almost everything transfers. Antigravity CLI is built on the same agent harness as Gemini CLI. Your GEMINI.md files, MCP server configurations, and custom slash commands work without modification. The migration is a surface change, not a platform change.

Options & when to use each

Tool	Status	When to use
Gemini CLI	Being replaced (unpaid/Google One)	If you are already on it, continue until the migration date
Antigravity CLI	New, actively developed	Start new projects here. Migrate existing workflows when convenient
Antigravity IDE	Full-featured, stable	When you want a GUI with agent manager, artifacts, and visual diffing
npx @google/gemini-cli	Always available	Quick one-off tasks without installing anything

Build it

Step 1: Install Antigravity CLI

Download from antigravity.google/download. The installer handles the CLI and optional IDE components.

Step 2: Migrate from Gemini CLI

The migration path preserves existing configurations, context files, and custom slash commands. Antigravity CLI automatically points to the new directory structure without requiring manual updates to your workflow.

# Your existing Gemini CLI config lives at:
# ~/.gemini/config.yaml
# ~/.gemini/commands/   (custom slash commands)
# GEMINI.md              (project context)

# Antigravity CLI reads from the same locations initially.
# After migration, config moves to:
# ~/.antigravity/config.yaml

# Verify your setup migrated:
antigravity --version
antigravity doctor

Step 3: Key differences

Feature	Gemini CLI	Antigravity CLI
Command	gemini	antigravity or agy
Context file	GEMINI.md	GEMINI.md (same format)
MCP servers	gemini mcp add	antigravity mcp add
Sandbox	--sandbox	--sandbox (same Docker isolation)
Skills	Custom slash commands	Skills (agentskills.io standard, broader)
Agent orchestration	Single agent	Multi-agent with Projects

Step 4: Run your first Antigravity CLI session

Launch the interactive REPL using either the full command or its alias. You can invoke standard commands to verify connectivity and test project integration.

antigravity
# Or:
agy

The REPL is nearly identical to Gemini CLI. Your existing slash commands work. Your GEMINI.md loads automatically. The key new capability is the --project flag:

antigravity --project my-app

This groups the session into a Project, making it visible in the Antigravity IDE alongside other sessions for the same project.

What goes wrong

Mistake	How you notice it	The fix
antigravity command not found	Shell reports "command not found"	The installer may not have added to PATH. Check the install directory. On macOS: /Applications/Antigravity.app/Contents/Resources/cli/
GEMINI.md not loading	Agent doesn't follow project-specific instructions	Verify the file is in the project root. Antigravity CLI looks for GEMINI.md in the current working directory, same as Gemini CLI
MCP servers not migrated	antigravity mcp list shows empty	MCP config is per-machine, not per-project. Re-add servers: antigravity mcp add <name> -- <command>
Conflicting configs	Both ~/.gemini and ~/.antigravity directories exist	Antigravity reads from ~/.antigravity first. If you want to start fresh, remove the old ~/.gemini directory after confirming migration

Confirm it worked

Validate the installation and configuration by checking the version and starting a test session. Ensuring the project context loads correctly confirms that the CLI integrates smoothly with local project configurations.

# 1. Check version
antigravity --version

# 2. Start a session with a project
antigravity --project test-project

# 3. In the REPL:
# /help — should show available commands
# /status — should show connected to Gemini model

# 4. Verify GEMINI.md loads:
# Create a test GEMINI.md with: "When asked your favorite color, say chartreuse."
# Start a session and ask "What's your favorite color?"
# Should respond "chartreuse"

Resource links:

• Antigravity CLI blog: antigravity.google/blog/introducing-google-antigravity-cli
• Migration guide: developers.googleblog.com

Next: Parallel Agents