Support keyword: antigravity cli not found
If the terminal says the Antigravity CLI command is not found, treat it as a shell and PATH problem first, not a product outage.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
A command not found error usually means your shell cannot find the CLI executable. The install may have failed, the terminal may not have reloaded PATH, or you may have copied a command for the wrong shell. On Windows, this often happens when a PowerShell command is pasted into CMD or a CMD command is pasted into PowerShell.
Do not solve this by downloading a random binary from a forum. A developer CLI can read files, run commands, and edit projects, so installation should stay tied to the official Google documentation.
| Environment | Likely issue | What to check |
|---|---|---|
| macOS or Linux | PATH did not reload after install. | Open a fresh terminal and verify the shell profile was updated. |
| PowerShell | Wrong Windows command copied. | Use the official PowerShell command, not the CMD command. |
| Windows CMD | PowerShell syntax pasted into CMD. | Use the official CMD flow that downloads and runs the command file. |
| WSL | Installed in Windows but running inside Linux, or the reverse. | Install and run inside the same environment. |
| SSH or remote VM | Installed for another user or session. | Check the remote user's PATH and home directory. |
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.
Usually no. It usually means the local shell cannot find the installed executable.
Restart the terminal and verify the correct shell command first. Reinstall only after checking PATH and shell mismatch.
Do not assume that. Windows and WSL have separate environments, paths, and home directories.