Google Antigravity is an agentic development platform with a desktop app, terminal CLI, editor integrations, a standalone IDE, and a Python SDK. This guide covers the practical first setup for the desktop app or CLI, then shows how to create a project without handing an agent more access than you intend.
Check the supported platform first
For the Antigravity desktop app, Google lists macOS 12 Monterey or later on Apple Silicon or 64-bit Intel, Windows 10 64-bit or Windows 11, and Linux with glibc 2.28 or newer and glibcxx 3.4.25 or newer. The documented examples include Ubuntu 20 or newer, Debian 10 or newer, Fedora 36 or newer, and RHEL 8 or newer. Googlebook OS devices come with Antigravity pre-installed and use Google Play for updates or reinstallation.
If you only want the terminal, Google provides the Antigravity CLI for macOS, Linux, Googlebook Linux Terminal, Windows PowerShell, and Windows Command Prompt. The editor extension route is separate: the official guide lists VS Code on macOS, Linux, or Windows, IntelliJ-based IDEs, Visual Studio on Windows, Zed on macOS or Linux, and Xcode on macOS.
Install Antigravity
Desktop app
- Open the official Antigravity download page and choose the build for your operating system.
- On macOS, open the downloaded
Antigravity.dmgand drag Antigravity to Applications. When upgrading, choose Replace rather than Keep Both. - On Windows, run the downloaded
.exeand follow the setup wizard. - On Linux, extract the archive with
tar -xzf Antigravity.tar.gz, then launch./Antigravity. - On Googlebook OS, open Google Play to update or reinstall the pre-installed app.
Command-line interface
Use the installer matching your shell:
- macOS, Linux, or Googlebook Linux Terminal:
curl -fsSL https://antigravity.google/cli/install.sh | bash - Windows PowerShell:
irm https://antigravity.google/cli/install.ps1 | iex - Windows Command Prompt:
curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd
Before running an installer piped from the internet, inspect the official command and confirm that the URL is exactly antigravity.google. Review any shell-profile or PATH change, and use the documented --skip-path or --skip-aliases options when you do not want those changes. After installation, open a new terminal if needed and run agy --version to verify that the CLI is available.
Sign in and finish first-run setup
Launch Antigravity and select Sign in. For an individual account, complete the browser-based OAuth flow with your personal Google Account. For a company account, choose Business account, continue with Google Cloud, and complete the organization’s sign-in flow. The docs say that signing in on one local surface shares credentials with the other Antigravity surfaces on that environment.
On the CLI, an existing secure OS keyring session may sign you in silently. If there is no saved session, it opens the browser. Over SSH, agy prints a one-time authorization URL for you to open on your local computer, then asks you to paste back the authorization code.
On the CLI’s initial interactive configuration, choose a color scheme and rendering mode, then confirm workspace trust for the repository directory. Treat that trust prompt as a security boundary: only approve a folder you recognize and understand.
Create your first project
From the app or IDE
- Click New Project, shown as a folder with a plus sign.
- Use Add Folder to select a local Git repository or working directory, then click Create.
- Enter a small, specific task and press Enter.
- Choose Local mode for the active folders, or New worktree mode for an isolated Git worktree.
When the agent proposes edits or tool actions, read the plan and inspect the diffs before approving them. Keep approval prompts enabled. Do not grant unrestricted auto-approval, particularly for shell commands, file deletion, network access, credentials, or changes outside the project. Ask the agent to explain a command first, run risky commands yourself when practical, and keep backups or a clean Git branch.
From the CLI
Create or enter a project directory, then start the terminal interface:
mkdir agy-demo
cd agy-demo
agyType a first task. The CLI indexes the workspace and shows a proposed implementation. Press Ctrl + R to open Artifact Review, inspect the files and diffs, and approve only the changes you expect. If you ask it to run a test or script, review the exact command before confirming it. Exit with Ctrl + D or /exit.
Before you let an agent act
Start with a disposable repository or a clean branch, remove secrets from the workspace, and define which folders and files are in scope. Prefer read-only discovery first. Review every file change, terminal command, dependency installation, and external action. If the result is not what you expected, stop the session, revert the change, and investigate rather than approving the next step automatically.
Product and setup details were checked against the official Get started, Authenticate, and Download pages.