Troubleshooting Guide Contents
Diagnose the Antigravity Error Before Changing Anything
The phrase Antigravity not working can mean several different failures. Some are cloud-side model or account issues; others are local shell, installer, update, proxy, or MCP configuration issues. Treat the exact error text as the starting point. A generic reinstall wastes time when the real cause is a blocked API endpoint, a missing Node.js binary, or a workspace-specific MCP crash.
Start by copying the visible error message and checking where it appears. A launch failure usually points to the installer, operating system, or security tools. A sign-in loop points to account cookies, browser handoff, clock time, or network policy. Agent execution errors often involve model availability, quota, connection stability, MCP tools, or oversized context. Terminal errors usually involve PATH inheritance, Node.js, npx, npm, or shell policy.
Before asking for help, note the exact message, when it appears, your operating system and app build from About, whether it happens in a clean workspace, and recent changes to Node.js, PATH, a proxy, or MCP tools. Reproduce it with a small local project and one short prompt. Remove personal paths, email addresses, access tokens, cookies, API keys, and private source code before sharing logs. Do not post a complete debug archive publicly. These details help route an Antigravity not working report to the app, account, network, terminal, or workspace layer without repeating risky reinstall steps.
| Symptom | Likely cause | First fix |
|---|---|---|
| Agent execution terminated due to error | Temporary model route failure, account state, network instability, MCP crash, or context limit. | Restart the agent service, switch to a small test prompt in a clean workspace, then disable MCP servers only if the clean prompt works. |
| Model API cannot be reached | Firewall, proxy, DNS, unsupported location, expired sign-in, or service-side availability. | Confirm sign-in, test another network, allow Google AI endpoints, and retry after a short wait before changing project files. |
| exec: "npx": executable file not found in PATH | Antigravity was launched with a different environment than your terminal or Node.js is not installed. | Install Node.js LTS, verify npx in a normal terminal, then launch Antigravity from the same shell or fix the system PATH. |
| PowerShell execution policy is blocking npx | Windows policy prevents npm shim scripts from running. | Use a trusted Node.js install, adjust the user execution policy only if your organization allows it, or configure the MCP command to use cmd-safe invocation. |
| Installer opens but Antigravity still will not launch | Wrong architecture, old process, unsupported OS, security software, or damaged install directory. | Check system requirements, close every Antigravity process, install the correct x64, ARM64, Apple Silicon, Intel, apt, or dnf build. |
Quick Fixes That Solve the Most Common Failures
When the app opens but behaves strangely, check About and Google's official download page before changing settings. Close all app processes, use only the installer published there, relaunch Antigravity from the normal system shortcut, and verify the build. If the app still reports an old version, inspect stale shortcuts or duplicate installations.
Restart the agent service before changing settings. Use the command palette if the UI is responsive, close background Antigravity processes if it is not, then try a short prompt in an empty or small repository. A clean prompt helps you tell the difference between a general service problem and a workspace-specific tool or context problem.
Check the network path when the message mentions a model API, unsupported location, timeout, or high traffic. Disable unstable VPN hops, confirm your proxy policy, and try a different network only for diagnosis. If another network works, the app installation is probably fine and the fix belongs in firewall, DNS, proxy, or account access rather than in the project.
Step-by-Step Antigravity Recovery Workflow
Record the exact error and version
If it opens, note the build in About and copy the exact error before reinstalling.
Test a clean workspace
Try one short prompt in a clean folder; success points to workspace tools or project rules.
Repair the matching layer
Update only for build errors; fix PATH, shell policy, or the MCP command tied to the message.
Error-Specific Fix Paths
Use the section that matches the error text instead of applying every fix. This reduces the chance of damaging a working configuration while trying to solve a temporary outage.
Agent execution terminated due to error: focused checklist
Separate model routing from local tool crashes. Retry a one-line prompt in a clean folder. If it works, re-enable MCP servers one at a time and check the failing shell, npx, browser, or MCP step. If it fails too, refresh sign-in, switch networks, and wait. Record the failed step; repeatable local tool failures point to configuration, while failures before tools start suggest sign-in, routing, quota, or network conditions.
Fix agent execution terminated due to error
Open a small test folder and ask the agent to read one file. If that fails, refresh sign-in, restart Antigravity, switch models if available, and retry later. If it works but your repository fails, inspect MCP servers, large files, workspace rules, broken Git metadata, and oversized prompts.
Fix npx executable file not found in PATH
Install Node.js LTS from a trusted source, then open a new terminal and run node -v, npm -v, and npx -v. If those commands work in the terminal but fail inside Antigravity, the app inherited a different PATH. Launch it from the terminal once, or add the Node.js directory to the user or system PATH and fully restart the app.
Fix PowerShell execution policy blocks
On Windows, npm and npx may call PowerShell scripts that your policy blocks. Avoid downloading random fix scripts. If you control the machine, set a user-level policy approved by your organization or configure the relevant MCP command to run through cmd with the executable path. Corporate machines should use IT-approved policy changes.
Fix sign-in loops and model API failures
Check your system clock, default browser, cookies, and account session. Sign out and back in, then test a small request. If the error mentions location, quota, or high traffic, reinstalling usually will not help. Try again later or verify whether your network and account are allowed to reach the model provider.
Fix install and update failures
Match the installer to your platform: Windows x64 or ARM64, macOS Apple Silicon or Intel, and repository packages on supported Linux distributions. Close old processes, remove stale shortcuts, and verify that the About dialog shows the new version after installation. Use old versions only for temporary rollback testing.
App and version layer
Compare About with Google's page, close app processes, and check the shortcut target after relaunch.
Agent and model layer
Try a clean prompt and a trusted network to separate workspace, account, network, and service failures.
Terminal, Node.js and MCP layer
Check node, npx, PATH, shell policy, and the named MCP command in an external terminal.
How to Prevent Antigravity From Breaking Again
After changing Node.js or PATH, restart the whole app and compare node and npx with your normal terminal.
Back up project settings before clearing caches; test MCP servers one at a time, and run only shell commands you understand.
Safety note
Do not run copied PowerShell, curl, or shell commands from random pages unless you understand exactly what they do. Troubleshooting an IDE should not require granting unknown scripts access to your code, tokens, or browser session.
Useful Official and Internal Links
Use these pages to verify the installer, compatibility, and update path after you identify the failure category.
- Official Antigravity download page - Google's official installer destination
- Official Antigravity CLI troubleshooting - official CLI and command-line troubleshooting reference
- Antigravity system requirements - check OS, architecture, RAM, storage, and network readiness
- Antigravity update guide - fix out-of-date warnings and stale old-version shortcuts