Antigravity CLI Cheatsheet: Commands, Setup, Shortcuts, and Workflows

Antigravity CLI is Google’s new CLI AI coding agent for working with Google’s new Antigravity agent.

It enables you to start, monitor, and control AI coding agents from the command line while using the same core agent harness as Antigravity 2.0.

Learn More About Antigravity CLI

This cheatsheet is for moments when you already know what you want to do and need the exact command.

Start with the quick reference table, then use the sections below for setup, slash commands, shortcuts, permissions, sandbox settings, subagents, MCP, and Gemini CLI migration.

Last updated: June 16, 2026

Antigravity CLI Cheatsheet

Table Of Contents

Antigravity CLI quick reference
Install Antigravity CLI
Authentication and SSH login
Core slash commands
Keyboard shortcuts
Settings, permissions, and sandbox
Subagents, tasks, skills, plugins, and MCP
Gemini CLI migration
Example Workflows
Troubleshooting tips

Antigravity CLI quick reference

Task	Command
Start CLI	`agy`
Command menu	`/`
Help	`?`, `/usage`
Settings	`/config`, `/settings`
Permissions	`/permissions`
File diff	`/diff`
Resume session	`/resume`
Rewind session	`/rewind`, `/undo`
Fork session	`/fork`, `/branch`
Add folder	`/add-dir <path>`
Open file	`/open <path>`
Run shell command	`!<command>`
Subagents	`/agents`
Task logs	`/tasks`
Skills	`/skills`
MCP servers	`/mcp`
Hooks	`/hooks`
Log out	`/logout`
Exit	`/exit`

Install Antigravity CLI

Antigravity CLI installs the agy binary. It runs on macOS, Linux, and Windows.

macOS and Linux

The native installer downloads the executable to ~/.local/bin/agy.

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

Windows PowerShell

The Windows installer registers agy in the local user directory at C:\Users\<Username>\AppData\Local\agy\bin.

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

Install flags

Flag	Use
`--skip-aliases`	Keep existing `agy` or `antigravity` aliases.
`--skip-path`	Do not edit shell profile `PATH`.

Authentication and SSH login

When you run agy locally, the CLI checks your operating system keyring first. On macOS it uses Apple Keychain. On Linux it uses Secret Service or dbus. On Windows it uses Windows Credential Manager. If a valid token exists, Antigravity CLI signs in silently.

If no saved session exists, the CLI opens your default browser. Sign in with your approved account, then return to the terminal.

SSH login uses a manual browser loop:

Run agy in the remote terminal.
Copy the authorization URL printed by the CLI.
Open the URL in a local browser.
Sign in and copy the authorization code.
Paste the code back into the remote terminal.

Use /logout when you need to disconnect the current account and purge saved authentication profiles.

Core slash commands

Slash commands are the fastest way to control Antigravity CLI. Type / in the prompt box to open the command menu.

Workspace and files

Command	Purpose
`/add-dir <path>`	Add a directory path to the active workspace.
`/diff`	Show unified diffs for modified workspace files.
`/open <path>`	Open a path in the default system editor.
`/clear`	Clear the terminal and reset active conversation context.

Conversation control

Command	Purpose
`/resume` (`/switch`, `/conversation`)	Load previous threads.
`/rewind` (`/undo`)	Roll back conversation history.
`/fork` (`/branch`)	Create a parallel session.
`/rename <name>`	Rename the thread.
`/exit`	Close the CLI.

Settings and agent behavior

Command	Purpose
`/config` or `/settings`	Open the interactive settings editor.
`/permissions`	Switch global permission presets.
`/model`	Choose the preferred reasoning model for future sessions.
`/planning`	Enable multi-turn plan generation mode for complex engineering tasks.
`/fast`	Enable fast mode for quick actions.
`/keybindings`	Open the keyboard shortcut editor.
`/statusline`	Customize the status bar.
`/title [on/off]`	Toggle or set terminal window title updates.

Tools, subagents, and accounts

Command	Purpose
`/agents`	Open the Agent Manager Panel for background subagents.
`/tasks`	Open the Task Manager Panel for background shell logs.
`/skills`	Browse loaded local and global Agent Skills.
`/mcp`	Open the MCP server manager.
`/hooks`	Browse active pre-flight and post-format hooks.
`/btw <query>`	Ask a side question in the background without interrupting the main conversation.
`/usage`	Open the offline developer help manual.
`/logout`	Disconnect the account and remove saved tokens.

Keyboard shortcuts

Keybindings can change if you customize them. Use /keybindings to inspect or edit your current setup.

Shortcut	Action
`Enter`	Submit the prompt or selected menu item.
`Shift+Enter` or `Ctrl+J`	Insert a newline without submitting.
`Alt+Enter`	Insert a newline in prompt editing.
`Esc`	Close panels, stop active streams, or clear an empty prompt.
`Ctrl+C`	Cancel or exit behavior, with confirmation when work is active.
`Ctrl+D`	Exit the TUI session.
`Ctrl+L`	Clear the visual terminal buffer.
`Ctrl+V`	Paste text, clipboard blocks, or terminal media.
`Ctrl+G`	Open the default shell editor for prompt composition.
`Ctrl+O`	Expand or collapse detailed tool reasoning output.
`Ctrl+R`	Open the Artifact Review Panel.
`Alt+J`	Switch focus to the next subagent awaiting confirmation.
`Ctrl+K`	Approve a pending subagent action from the fast path alert.
`Ctrl+A`	Move the prompt cursor to the start of the line.
`Ctrl+E`	Move the prompt cursor to the end of the line.
`Ctrl+Z`	Undo the last text edit.
`Ctrl+Shift+Z`	Redo the last undone text edit.
`Up` and `Down`	Move through menu selections.
`PgUp` or `Shift+Up`	Scroll the active viewport up by one page.
`PgDn` or `Shift+Down`	Scroll the active viewport down by one page.
`Tab`	Confirm the highlighted slash-command autofill option.
`y`	Approve a proposed tool, command, or artifact.
`n`	Reject a proposed tool, command, or artifact.
`A`	Approve all generated artifacts inside the Review Panel.

Settings, permissions, and sandbox

Antigravity CLI stores its main settings in:

~/.gemini/antigravity-cli/settings.json

It stores custom keybindings in:

~/.gemini/antigravity-cli/keybindings.json

You can edit settings through /config or /settings. Some settings can also be overridden at launch with flags such as --sandbox or --dangerously-skip-permissions. A launch flag applies to the current session until restart, even if you edit the persistent setting on disk.

Settings worth knowing

Setting	Default and use
`colorScheme`	`"terminal"`; color theme.
`altScreenMode`	`"default"`; screen buffer.
`toolPermission`	`"request-review"`; tool approvals.
`artifactReviewPolicy`	`"asks-for-review"`; code review flow.
`notifications`	`false`; completion alerts.
`showTips`	`true`; prompt tips.
`showFeedbackSurvey`	`true`; feedback prompts.
`editor`	`"auto"`; external editor.
`allowNonWorkspaceAccess`	`false`; outside-root file access.
`enableTerminalSandbox`	`false`; command sandboxing.
`enableTelemetry`	`true`; metrics and crash logs.
`verbosity`	`"high"`; output detail.
`runningLightSpeed`	`"medium"`; progress animation.

Permission presets

Preset	Use
`request-review`	Default for most coding work.
`proceed-in-sandbox`	Auto-proceed inside sandbox.
`always-proceed`	No prompts; controlled workspaces only.
`strict`	Prompt for all non-read tools.

Terminal sandbox

Set enableTerminalSandbox to true if you want local agent commands to run inside OS containment boundaries.

{
  "enableTerminalSandbox": true
}

When sandbox mode is enabled, Antigravity CLI can still ask whether a trusted command should run without sandbox restrictions. When sandbox mode is disabled, a confirmation prompt can offer to run a specific risky command inside the sandbox.

For regular project work, start with request-review, keep allowNonWorkspaceAccess set to false, and inspect /diff before accepting code changes.

Subagents, tasks, skills, plugins, and MCP

Antigravity CLI can run background subagents. The main agent can delegate work such as documentation lookup, builds, tests, and validation while the primary conversation stays active.

Use /agents to open the Agent Manager Panel. It shows active and completed subagents, their status, and the step each subagent is running. Select a subagent to inspect its full conversation, tool logs, and pending approvals.

Use /tasks when you need shell execution logs. Use /skills to browse loaded Agent Skills. Use /mcp to manage Model Context Protocol servers. Use /hooks to inspect active pre-flight and post-format hooks.

Plugins are staged under:

~/.gemini/antigravity-cli/plugins/<plugin_name>/

A plugin can include a required plugin.json file plus optional mcp_config.json, hooks.json, skills/, agents/, and rules/ directories.

Gemini CLI migration

Antigravity CLI supports migration from Gemini CLI. On first launch, agy can detect legacy Gemini CLI profiles and prompt you to choose which assets to migrate.

The migration flow can import extensions, global configuration, active session tokens, visual settings, workspace rules, skills, and MCP server definitions. Some customized terminal themes or experimental visual overlays may not have full parity.

Convert Gemini extensions to Antigravity plugins

Run:

agy plugin import gemini

The importer searches legacy local directories, reads extension manifests, and converts compatible files into Antigravity plugin layout blocks.

Context files

Antigravity CLI continues to read workspace context from:

GEMINI.md
AGENTS.md

It also consults global developer context at:

~/.gemini/GEMINI.md

Skills path changes

Scope	Path change
Global skills	`~/.gemini/skills/` to `~/.gemini/antigravity-cli/skills/`
Workspace skills	`.gemini/skills/` to `.agents/skills/`

If a project has custom workspace skills in .gemini/skills/, move or rename that folder to .agents/skills/ so Antigravity can recognize those skills as active slash commands.

MCP config changes

Gemini CLI declared MCP servers inside:

~/.gemini/settings.json

Antigravity CLI uses standalone MCP profiles:

~/.gemini/config/mcp_config.json
.agents/mcp_config.json

For remote websocket or SSE server definitions, update legacy url or httpUrl fields to serverUrl.

{
  "mcpServers": {
    "remote-indexer": {
      "serverUrl": "https://mcp.internal.enterprise.com/sse",
      "env": {
        "AUTH_TOKEN": "secure_alpha_token"
      }
    }
  }
}

Example Workflows

Start work in a repository

cd path/to/project
agy

In the prompt, describe the task and scope. Keep the first request narrow. For example:

Review this repository and identify the files involved in the login flow. Do not edit files yet.

Add another folder to the workspace

/add-dir ../shared-package

Use this when the agent needs access to a sibling package, shared library, or local dependency.

Run a terminal command

!npm test

Use ! for commands you would normally run yourself. Keep review prompts enabled when a command can modify files, install dependencies, or reach the network.

Review changes before accepting them

/diff

Read the diff before accepting a change. If the change is too broad, ask the agent to narrow the edit or explain the affected files.

Rewind a bad turn

/rewind

Use /rewind or /undo when the conversation goes in the wrong direction. This rolls back conversation history to a previous message.

Fork an approach

/fork

Use /fork when you want to explore a different solution without losing the current thread.

Resume earlier work

/resume

Use /resume to reopen previous conversation logs. Antigravity CLI also prints the command needed to resume a specific session when you close the CLI.

Use subagents without losing focus

/agents

Open /agents when background work needs your approval or when you want to inspect what a subagent did. Use Ctrl+K for fast approval when a pending subagent action appears above the prompt.

Keep output quieter

/config

Set verbosity to low if many tool calls make the terminal hard to scan.

Troubleshooting tips

Problem	Fix
`agy` not found	Check `PATH` and install directory.
SSH sign-in stalls	Open the printed URL locally and paste the code.
Agent cannot see a folder	Use `/add-dir <path>` or start in project root.
Output is noisy	Set `verbosity` to `low`.
Command needs tighter safety	Use `strict` or enable sandboxing.
Workspace skill stopped working	Move `.gemini/skills/` to `.agents/skills/`.
MCP config fails	Use `mcp_config.json` and `serverUrl`.
Need to inspect code	Use `/diff`, then `Ctrl+R`.
Reset custom shortcuts	Delete `keybindings.json`.

Related Resources

FAQs

What command starts Antigravity CLI?

Run agy from your terminal.

What is the fastest way to see available commands?

Type / in the prompt box to open the slash command menu. Type ? for help or /usage for the offline developer manual.

Where does Antigravity CLI store settings?

It stores main settings at ~/.gemini/antigravity-cli/settings.json and custom keybindings at ~/.gemini/antigravity-cli/keybindings.json.

How do I review code changes?

Use /diff to inspect modified files. Use Ctrl+R to open the Artifact Review Panel.

How do I undo a bad conversation turn?

Use /rewind or /undo to roll conversation history back to an earlier message.

How do I migrate from Gemini CLI?

Start agy in an environment that contains legacy Gemini CLI profiles and follow the first-launch checklist. To convert Gemini extensions manually, run agy plugin import gemini.

Does Antigravity CLI support MCP?

Yes. Use /mcp to open the MCP server manager. Global MCP servers use ~/.gemini/config/mcp_config.json, and workspace servers use .agents/mcp_config.json.

Should I use `always-proceed`?

Use always-proceed only in controlled workspaces where you are comfortable with the agent acting without prompts. For most coding work, request-review is safer.

How do I make Antigravity CLI quieter?

Open /config and set verbosity to low.