Google Antigravity Troubleshooting Guide

Solutions:

• Run the installer as Administrator (right-click → Run as administrator)
• Disable antivirus temporarily during installation
• Ensure you have at least 2GB free disk space
• Check Windows Defender isn't blocking the installer
• Install Visual C++ Redistributable if missing

Solutions:

• Go to System Preferences → Security & Privacy → General
• Click "Open Anyway" for Google Antigravity
• Alternatively: Right-click app → Open → Click "Open"
• For M1/M2 Macs: Ensure you downloaded the ARM version

Ubuntu/Debian:

sudo apt update
sudo apt install libgtk-3-0 libnotify4 libnss3 libxss1 \
                 libxtst6 xdg-utils libatspi2.0-0 libdrm2 \
                 libgbm1 libasound2

Fedora/RHEL:

sudo dnf install gtk3 libnotify nss libXScrnSaver \
                 libXtst xdg-utils at-spi2-core alsa-lib

Solutions:

• Verify extension is installed: chrome://extensions
• Ensure extension is enabled (toggle should be blue)
• Check that Antigravity desktop app is running
• Click extension icon → "Reconnect to Antigravity"
• Restart Chrome completely (close all windows)
• Check firewall isn't blocking localhost connections

Solutions:

• Grant all requested permissions during installation
• Check extension permissions: chrome://extensions → Details → Permissions
• Enable "Allow access to file URLs" if working with local files
• For incognito mode: Enable "Allow in incognito"
• Some enterprise sites block extensions - check with IT

Solutions:

• Remove and reinstall the extension
• Clear extension cache: chrome://extensions → Remove → Reinstall
• Update Chrome to the latest version
• Disable other conflicting extensions temporarily
• Check Chrome Task Manager (Shift+Esc) for memory issues

Solutions:

• Verify your API key is correct (check for extra spaces)
• Ensure you're using the correct key for your model (Gemini, Claude, or GPT)
• Check if your API key has expired or been revoked
• Regenerate API key from the provider's dashboard
• Clear saved credentials and re-authenticate

Solutions:

• Clear browser cookies and cache
• Disable third-party cookie blocking for antigravity.google
• Try signing in with an incognito window
• Check if corporate VPN is interfering with OAuth
• Ensure popup blocker isn't blocking the auth window

Solutions:

• Check system clock is accurate (OAuth is time-sensitive)
• Enable "Keep me signed in" option
• Whitelist *.antigravity.google in your firewall
• Update to the latest version of Antigravity

Solutions:

• Wait: Rate limits typically reset after 60 seconds to 1 hour
• Reduce agent count: Limit concurrent agents to 2-3 instead of 5+
• Use async mode: Enable async workflows to queue requests
• Switch models: Try a different model if one is throttled
• Upgrade plan: Consider upgrading for higher quotas
• Check usage: Monitor your quota in Settings → Usage

Solutions:

• Check your billing status and current quota
• Wait until the next billing cycle for quota reset
• Purchase additional quota if available
• Use more efficient prompts to reduce token usage
• Enable caching for repeated queries

Solutions:

• Check you haven't hit the maximum agent limit (default: 10)
• Verify API keys are configured correctly
• Check system resources (RAM > 4GB available)
• Restart the Agent Manager: View → Agent Manager → Restart
• Look for errors in the console: Help → Developer Tools
• Update to the latest version

Solutions:

• Use more specific task descriptions
• Assign agents to specific workspaces
• Enable workspace isolation in settings
• Use task dependencies to control execution order
• Review Agent Manager to verify task assignments

Solutions:

• Enable file locking: Settings → Agents → File Lock Mode
• Assign different modules/directories to different agents
• Use sequential mode instead of parallel for related tasks
• Review artifact system for conflict resolution
• Set up agent communication channels for coordination

Solutions:

• Check agent status in Agent Manager
• Set timeout limits: Settings → Agents → Task Timeout
• Manually terminate stuck agent: Agent Manager → Select → Terminate
• Check if agent is waiting for user input
• Review agent logs for errors or infinite loops

Solutions:

• Reduce number of concurrent agents
• Close unused workspaces
• Clear artifact cache: Settings → Storage → Clear Cache
• Disable browser integration if not needed
• Limit context window size: Settings → Models → Context Limit
• Restart Antigravity periodically during long sessions

Solutions:

• Check your internet connection speed
• Switch to a faster model (e.g., Gemini Flash instead of Pro)
• Reduce context size by being more specific in prompts
• Enable response caching for repeated queries
• Use streaming mode for faster perceived response
• Check server status at status.antigravity.google

Solutions:

• Update to the latest stable version
• Check crash logs: Help → Show Logs
• Disable experimental features
• Increase system RAM if below 8GB
• Reset to default settings: Settings → Advanced → Reset
• Reinstall Antigravity if crashes persist

Common Problems:

• Path length limit: Enable long paths via Group Policy or Registry
• Windows Defender: Add Antigravity to exclusion list
• PowerShell execution: Set execution policy to RemoteSigned
• WSL integration: Ensure WSL2 is installed for Linux workspace support

Common Problems:

• M1/M2 compatibility: Use ARM version, not Intel
• Rosetta: Intel version requires Rosetta 2 on Apple Silicon
• Permissions: Grant Full Disk Access: System Preferences → Security
• Command line tools: Install Xcode CLI tools first

Common Problems:

• Wayland: May need to force X11 mode for some features
• AppImage permissions: chmod +x antigravity.AppImage
• Sandbox issues: Run with --no-sandbox flag if needed
• Font rendering: Install Microsoft fonts for better UI

Solutions:

• Check internet connection is stable
• Verify firewall allows outbound HTTPS (port 443)
• Test connectivity: ping antigravity.google
• Try different DNS servers (8.8.8.8, 1.1.1.1)
• Disable VPN temporarily to test
• Increase timeout: Settings → Network → Request Timeout

Solutions:

• Request IT to whitelist: *.antigravity.google, *.googleapis.com
• Configure proxy settings: Settings → Network → Proxy
• Use enterprise SSO if available
• Check SSL inspection isn't breaking connections

Solutions:

• Auto-detect proxy: Settings → Network → Auto-detect
• Manual configuration: HTTP_PROXY and HTTPS_PROXY environment variables
• Test proxy: curl -x proxy:port https://antigravity.google
• Bypass proxy for local: Add localhost, 127.0.0.1 to no_proxy

Solutions:

• Install the official Antigravity VSCode extension
• Restart VSCode after installing extension
• Check extension is enabled: Extensions → Antigravity → Enable
• Verify connection: Command Palette → "Antigravity: Connect"
• Update both VSCode and Antigravity to latest versions

Solutions:

• Configure Git: git config --global user.name and user.email
• Enable auto-commit: Settings → Git → Auto Commit
• Review agent changes before committing
• Use branch per agent for parallel development
• Check SSH keys are configured for private repos

Solutions:

• Set default shell: Settings → Terminal → Shell Path
• Configure environment variables in terminal profile
• Enable terminal in workspace: View → Terminal
• Check shell initialization files (.bashrc, .zshrc) for errors

Solutions:

• Check file/folder permissions: ls -la (Linux/Mac) or icacls (Windows)
• Grant read/write access to workspace directories
• Run Antigravity with appropriate user privileges
• Don't run as root/admin unless necessary
• Check if files are locked by another application

Solutions:

• Grant workspace access: File → Open Folder → Allow
• Check .gitignore or .antigravityignore patterns
• Verify symbolic links point to valid locations
• Ensure files aren't on network drives with access issues
• Check encoding: Use UTF-8 for all source files

Solutions:

• Use .antigravityignore to exclude large files (node_modules, build/, etc.)
• Increase file size limit: Settings → Files → Max File Size
• Enable selective workspace loading
• Use shallow git clones for large repos
• Consider splitting monorepos into multiple workspaces