Paste an error to match it against the wiki. / 粘贴报错后自动匹配。
Error text / 报错原文
Agent execution terminated due to errorAgent terminated due to errorModel API cannot be reached
What it means
The Antigravity agent runner stopped before completing the task. The cause can be provider reachability, model routing, MCP tool failure, or stale local auth.
Most common causes
- Backend or model route temporarily unavailable
- MCP server crashes during tool discovery
- A long chat or large tool payload hits request limits
- Google account token state is stale
Fastest fix
- Start a new small task in a new chat
- Disable MCP servers and retry
- Sign out and back in if other network calls fail
- Switch model if the failure is model-specific
Safe fix
- Re-enable MCP servers one at a time
- Keep project rules short and path-scoped
- Avoid running production-changing commands until the agent is stable
- Capture logs before reinstalling
What not to do
- Do not delete project files while fixing an IDE agent crash
- Do not hardcode Google tokens into MCP config
- Do not assume all model failures are local bugs
How to confirm the fix
Run the smallest reproducible command first, then retry the agent task only after authentication, quota, and tool discovery are stable.
node --version git status --short --branch echo %APPDATA%
Related errors
- Error calling initialize: EOF - Antigravity MCP →
- Failed to exchange authorization code for token - Antigravity →
- Failed to get OAuth token: state syncing error: key not found - Antigravity →
- Command exits 0 but captures zero stdout/stderr - Antigravity terminal blindness →
- Stuck on Running / Generating - Google Antigravity agent not responding →
- Antigravity doesn't support MCP OAuth specifications →