Antigravity Editor Common Errors Fix: AI Completion, Connection Issues & Project Loading Failures

Antigravity's editor is built for AI-native development, but like any sophisticated tool, it occasionally hits snags. "AI completion just stopped working." "My project won't open." "The terminal is completely frozen." Sound familiar?

Most of these issues trace back to connection problems, cache corruption, resource limits, or configuration drift — all fixable in minutes once you know where to look.

Issue #1: AI Code Completion Stopped Working

Symptom: No AI suggestions appearing, or completion is dramatically slower than usual.

Diagnostic steps

First, check the status bar in the lower right corner. "AI: Connecting" or "AI: Error" indicates a connection problem.

Next, check your credit balance in the account sidebar. Completion stops when credits reach zero. (See Antigravity Credits and Quota Guide for details.)

Common fixes, in order of likelihood:

1. Reload the window: Cmd/Ctrl + Shift + P → Developer: Reload Window
2. Switch AI model: Go to Settings → AI Model, switch to a different model, then switch back
3. Disable VPN temporarily: VPNs occasionally intercept WebSocket connections that AI completion depends on
4. Check for extension conflicts: If you have GitHub Copilot or another completion extension installed, they can interfere

# Check editor logs for error patterns:
# Menu → Help → Toggle Developer Tools → Console tab
#
# Common error signatures:
# "Network error" or "Failed to fetch" → connection problem
# "Authentication failed" or "401" → re-login needed
# "Rate limit exceeded" or "429" → quota or rate limit hit
# "WebSocket closed" → unstable connection, often VPN-related

Issue #2: Project Won't Open / Empty File Tree

Symptom: Clicking a project does nothing, or the project opens but shows an empty file explorer.

Root cause A: File watcher limit exceeded

Large projects (with node_modules, .git, build outputs) can exhaust the OS file watcher limit.

# macOS: check and raise the limit
launchctl limit maxfiles
# Example output: maxfiles 256 unlimited
 
# Raise it (takes effect immediately, no restart needed)
sudo launchctl limit maxfiles 65536 200000
 
# Linux: raise the inotify limit permanently
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

Root cause B: Corrupted workspace cache

# Clear Antigravity's workspace cache
# macOS
rm -rf ~/Library/Application\ Support/Antigravity/Cache/
rm -rf ~/Library/Application\ Support/Antigravity/Workspaces/
 
# Linux
rm -rf ~/.config/antigravity/Cache/
rm -rf ~/.config/antigravity/workspaces/
 
# Windows: delete the folder at %APPDATA%\Antigravity\Cache\

Root cause C: File permission issues

# Check ownership and permissions
ls -la /path/to/project/
 
# Fix ownership (replace 'username' with your actual username)
sudo chown -R $(whoami) /path/to/project/
chmod -R u+rw /path/to/project/

Issue #3: Terminal Frozen or Unresponsive

Symptom: Commands typed into the integrated terminal don't run, or a previous command never finishes.

# Step 1: Kill the foreground process
Ctrl + C
 
# Step 2: If that doesn't help, open a new terminal
Ctrl + Shift + ` (backtick)  # or Cmd + Shift + `
 
# Step 3: Find and kill stuck processes
ps aux | grep [process-name]
kill -9 [PID]
 
# Step 4: Reset the shell environment
exec $SHELL

When the terminal is completely frozen: The fastest fix is reloading the window (Cmd/Ctrl + Shift + P → Developer: Reload Window). If you have a long-running task you can't interrupt (like a build), check its status in your system's Activity Monitor / Task Manager before force-quitting.

Issue #4: Git Integration Not Working

Symptom: Source Control panel shows no changes, or Git operations fail with errors.

# Verify Git is configured correctly
git config --list --global | grep -E "user.name|user.email"
 
# Set them if missing
git config --global user.name "Your Name"
git config --global user.email "your@email.com"
 
# Test SSH authentication (for GitHub/GitLab)
ssh -T git@github.com
# Expected: "Hi username! You've successfully authenticated..."
 
# Test HTTPS authentication
git ls-remote https://github.com/username/repo.git

Git operations slow on large repositories:

# Add build artifacts and dependencies to .gitignore
echo "node_modules/" >> .gitignore
echo ".next/" >> .gitignore
echo "dist/" >> .gitignore
echo ".antigravity/" >> .gitignore
 
# Clean up Git history
git gc --auto
git remote prune origin

Issue #5: Extensions Not Working or Failing to Install

Symptom: Installed extension isn't activating, or installation throws an error.

Diagnose extension conflicts by launching without extensions:

# macOS
/Applications/Antigravity.app/Contents/MacOS/Antigravity --disable-extensions
 
# Or from command line
antigravity --disable-extensions /path/to/project

If the problem disappears with --disable-extensions, enable extensions one at a time (restart after each) to find the conflict.

Manual extension installation from .vsix file:

Menu → Extensions → ··· (More Actions) → Install from VSIX...

Clear extension data if an extension is stuck:

# macOS — inspect and remove the problematic extension folder
ls ~/Library/Application\ Support/Antigravity/extensions/
# Identify the folder for the broken extension and remove it
rm -rf ~/Library/Application\ Support/Antigravity/extensions/[extension-id]-[version]/

Looking back

The most common Antigravity editor issues and their fixes:

• AI completion stops → Reload window, check credit balance, disable VPN
• Project won't open → Raise file watcher limits, clear workspace cache
• Terminal frozen → Ctrl+C → new terminal → reload window (in that order)
• Git not working → Verify user config, check SSH auth, add large folders to .gitignore
• Extensions failing → Use --disable-extensions to isolate the conflict

A window reload (Developer: Reload Window) resolves a surprising number of transient issues before anything else. When it doesn't, follow the logs — the Developer Console almost always points directly at the root cause.