The Antigravity CLI is Google's terminal client for Antigravity agents, and you run it with the command agy. Google's launch post on May 19, 2026 called it the most lightweight way to invoke, monitor and interact with Antigravity agents from your terminal, and the download page lists version 1.4.10 as of November 2026.
It uses the same agent harness as the Antigravity 2.0 App and shares its settings, so permissions you set in one carry over to the other. Conversations aren't shared by default, but you can pull a CLI conversation into the App from the @conversation dropdown. Google says it deliberately doesn't try to be a GUI: the App is built for the full feature set, the CLI for speed and low overhead.
Installing agy and checking the version
- On macOS, Linux or a Googlebook, run the one-line curl installer listed on the download page and in the getting started docs.
- On Windows, use the PowerShell installer or the CMD one-liner from the same download page.
- Check it worked with agy --version. On macOS and Linux the binary goes to ~/.local/bin/agy by default.
- Open a terminal in your project folder and run agy.
What the first launch asks you
The first run walks you through a short setup with three choices. They're quick, but the third one matters:
- Colour scheme: Dark, Solarized Dark, Solarized Light or your terminal's default.
- Rendering mode: Alt-Screen, which takes over the full screen, or Inline, which prints output in sequence.
- Workspace trust: you confirm you trust the repository before the agent starts indexing its files.
The four execution modes
Modes decide how much the agent can do before it checks with you. Press Shift+Tab to cycle through default, accept-edits, auto and plan, or launch straight into one, for example agy --mode=accept-edits or agy --mode=auto.
| Mode | File edits | Terminal commands |
|---|---|---|
| default | Pauses for an interactive diff review before any file changes | Asks before running |
| accept-edits | Approved automatically inside your workspace | Still asks before running |
| plan | Outlines the steps before writing any code | Not covered in the mode summary |
| auto (Preview) | Approved for you | Runs in a sandbox and approves safe, reversible commands |
Here's the part most people miss. Auto mode is a Preview, needs CLI v1.3.5 or later on macOS and Linux, or v1.4.4 or later on Windows, plus the terminal sandbox. It isn't available for business or enterprise accounts at all, including Antigravity in Gemini Enterprise, and if it can't run the CLI simply starts in default mode.
Whatever mode you're in, explicit allow, ask and deny rules set with /permissions win, and so do global overrides such as --dangerously-skip-permissions. Subagents inherit the mode you pick, so in accept-edits mode their background file writes don't queue up waiting for you.
Reviewing an edit in default mode
Each edit shows an inline diff and the question Accept this file edit. Press 1 to accept, 2 to reject or f for a full-screen diff. A pending edit stays open until you decide, because Esc won't dismiss it. If the agent wants to create a file outside your workspace, you'll see an extra line that reads Reason: outside workspace.
Settings, keybindings and shortcuts
Settings live in a plain JSON file at ~/.gemini/antigravity-cli/settings.json. Type /config or /settings for a full-screen menu. Some settings can be overridden at launch with flags such as --sandbox, and the menu shows where each override came from. Keybindings are edited with /keybindings or in ~/.gemini/antigravity-cli/keybindings.json, and deleting that file resets them, though the exit and enter bindings can't be switched off.
| Type this | What happens |
|---|---|
| @ | Suggests file paths |
| ! at the start of a prompt | Runs a terminal command |
| ? | Lists the slash commands |
| esc esc | Clears the prompt |
| /rewind or /undo | Goes back in the conversation |
| /fork | Branches the conversation |
| /clear | Starts fresh |
| /resume | Lists earlier sessions |
When you close the CLI, it prints the exact command you'll need to resume that session, which saves hunting for it later.
Watching background subagents
Type /agents to open the subagents panel and watch background agent sessions as they run. Press ctrl+k to approve a tool instantly. Slash commands also give quick access to the plugins, MCP, skills and hooks settings. If your team already works with Claude Code, the idea will be familiar from subagents in Claude Code, though each tool sets them up its own way.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Plugins from the command line
The plugin directory that launched on October 29, 2026 works in the CLI too. Open the plugin manager with /plugin, switch between its Installed and Discover tabs, and install from the shell with agy plugin install followed by the plugin name.
Moving over from Gemini CLI
If your team used Gemini CLI, most of the switch is automatic. On the first agy launch in an environment with older configuration, the CLI offers an interactive checklist to migrate extensions and settings, and moves session tokens into your operating system's keyring. Run agy plugin import gemini to turn old extensions into plugins. If you never set Gemini CLI up, my guide to using Gemini CLI explains what you'd be moving from.
- Carries over: your GEMINI.md and AGENTS.md context files, including the global one at ~/.gemini/GEMINI.md.
- Rename by hand: workspace skills move from .gemini/skills/ to .agents/skills/, and they won't be recognised until you rename the folder yourself.
- New home for MCP: servers sit in a standalone mcp_config.json, globally at ~/.gemini/config/mcp_config.json or per project at .agents/mcp_config.json, and remote servers use the key serverUrl instead of url or httpUrl.
- May not survive: Google warns some Gemini CLI themes and experimental overlays won't carry over.
My safe default
I'd start every new repository in default mode, so you see each diff and every command before it runs, and only press Shift+Tab to accept-edits once you trust the task. I wouldn't plan your workflow around auto mode if you're on a business or enterprise account, because it's switched off there. And if you're coming from Gemini CLI, rename the skills folder on day one, because that's the one step the migration checklist won't do for you.
Frequently asked questions
What is the command for the Antigravity CLI?
The command is agy. You check the installed version with agy --version, and the download page lists version 1.4.10 as of November 2026.
Where are the Antigravity CLI settings stored?
In a plain JSON file at ~/.gemini/antigravity-cli/settings.json. You can also type /config or /settings for a full-screen settings menu.
Why can't I use auto mode in the Antigravity CLI?
Auto mode is a Preview that needs CLI v1.3.5 or later on macOS and Linux, or v1.4.4 or later on Windows, plus the terminal sandbox. It isn't available for business or enterprise accounts.
Do my Gemini CLI skills work in Antigravity CLI?
Yes, but you have to move them. Workspace skills go from .gemini/skills/ to .agents/skills/, and you rename that folder yourself.
