Support keyword: antigravity cli troubleshooting
When Antigravity CLI feels broken, check auth, shell type, permissions, migration files, MCP config, and workspace context before reinstalling.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
Not affiliated with Google. No binaries, mirrors, login forms, or copied install commands are hosted here.
| Symptom | Likely cause | First check |
|---|---|---|
| Auth opens wrong browser or fails remotely | Remote or SSH session flow differs from local sign-in. | Use the printed authorization URL/code flow instead of entering credentials in the terminal. |
| Command not found after install | PATH not refreshed or wrong shell command used. | Restart terminal and verify the install command matched your shell. |
| Skills missing after migration | Workspace-specific skill paths changed. | Check global skills and project .agents/skills. |
| MCP server not loading | Config file path or remote field naming changed. | Open the migration docs and compare expected MCP config. |
| Agent wants too many approvals | Permissions are conservative. | Open /permissions, but only loosen settings in a safe branch. |
| Agent does too much | Autonomy or sandbox settings are too broad. | Re-enable review, use Git diff, and reduce permissions. |
Reinstalling is tempting, but many CLI problems are configuration or migration issues. Check the official docs, confirm your shell, inspect settings, and test in a clean folder. If you migrated from Gemini CLI, compare skill and MCP locations before assuming the new CLI ignored your setup.
Ask for help after you can share the operating system, shell type, whether the session is local or remote, what command failed, and whether the issue happens in a brand-new empty folder. This keeps community threads useful and makes the problem easier to reproduce.
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.
Remote sessions often use an authorization URL and code flow instead of opening the browser directly.
Migration can involve different skill paths and management behavior. Check the official migration docs.
Yes, if each page answers a distinct problem and links back to the main guide.