Support keyword: antigravity cli install
Use the official command for your operating system, then verify authentication before moving real projects into Antigravity CLI.
Updated on 2026-05-26. Independent guide. Use official Google links for downloads and account actions.
Official command picker
Commands shown here mirror the current official Google documentation. Always re-check the official docs before production rollout.
curl -fsSL https://antigravity.google/cli/install.sh | bash
After installation, authenticate, inspect /permissions, and test in a disposable folder first.
The safest install flow is boring on purpose: start from the official Antigravity download page, read the current requirements, then run the command that matches your shell. Do not use random mirrors, reposted installers, or short-link commands for a developer tool that can read and edit local files.
Google's current documentation lists one command for macOS and Linux, one for Windows PowerShell, and one for Windows CMD. The CLI then attempts secure keyring authentication and falls back to a Google Sign-In flow when needed. Remote or SSH sessions may show an authorization URL that you open in a local browser.
/config and /permissions to inspect safety settings.If sign-in fails on a remote server, do not paste your Google password into the terminal. Use the browser URL or authorization code flow described by the CLI.
PowerShell uses irm. CMD uses curl to download and run a command file. Copy the right one.
Do not install from unofficial file hosts. A CLI that can edit projects should come from the official source.
After installation, review permissions before trying yolo-style autonomous workflows or large refactors.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
The current official command shown by Google is curl -fsSL https://antigravity.google/cli/install.sh | bash.
No. PowerShell uses the official irm install.ps1 command. Windows CMD uses a different curl command.
You can install first, but review the migration guide before deleting Gemini CLI settings, skills, or MCP configuration.