Skip to main content

Overview

This page covers the most common issues users encounter when using Antigravity Manager and provides step-by-step solutions.

Application Issues

Symptoms:
  • Application exits immediately after launch
  • Black screen or frozen window
  • Error message on startup
Solutions:
  1. Check log files for error messages:
  2. Clear application cache:
    • Close the application completely
    • Delete the cache directory:
  3. Reset configuration:
    This will remove all your settings. Back up your gui_config.json first.
  4. Reinstall the application using the latest version from GitHub Releases
Symptoms:
  • Client applications cannot connect to http://127.0.0.1:8045
  • “Connection refused” errors
  • API requests timeout
Solutions:
  1. Verify proxy service is running:
    • Open Antigravity Manager
    • Navigate to “API Proxy” page
    • Check if the service toggle is enabled (green)
  2. Check port conflicts:
  3. Verify firewall settings:
    • macOS: System Preferences → Security & Privacy → Firewall
    • Windows: Windows Defender Firewall → Allow an app
    • Ensure Antigravity Tools is allowed
  4. Test the connection:
  5. Check API key configuration:
    • Ensure your client is using the correct API key (default: sk-antigravity)
    • Verify the API key matches the one in Settings → API Proxy
Symptoms:
  • Accounts automatically marked as “Disabled”
  • Frequent invalid_grant errors in logs
  • Account shows as forbidden (403)
Solutions:
  1. Re-authorize the account:
    • Go to Accounts page
    • Click on the disabled account
    • Click “Delete” to remove the account
    • Add the account again using OAuth
  2. Check for token expiry:
    • The refresh token may have been revoked
    • Ensure you’re not using the same Google account in multiple instances
  3. Verify account permissions:
    • Ensure the account has access to required Google services
    • Check if the account requires verification (see Account Errors)
  4. Review proxy settings:
    • If using a proxy pool, verify proxy credentials are correct
    • Check if proxies are working correctly
See Account Errors for detailed error handling.
Symptoms:
  • Dashboard shows 0% quota for models
  • Account can still make requests successfully
  • Manual refresh doesn’t update quota
Solutions:
  1. Force refresh quota:
    • Go to Accounts page
    • Click “Refresh All” button
    • Wait for the refresh to complete
  2. Check account type:
    • Free accounts have limited quota that resets frequently
    • Pro/Ultra accounts have different quota limits
    • Verify your account tier matches expectations
  3. Sync account from database:
    • Click the sync icon on the account card
    • This forces a fresh quota fetch from Google
  4. Clear quota cache:
Symptoms:
  • Application feels sluggish
  • High CPU or memory usage
  • Long delays when switching pages
Solutions:
  1. Clean up old logs:
    • Logs are automatically cleaned after 7 days
    • Maximum log size is capped at 1GB (512MB after cleanup)
    • Manually clear logs: Settings → About → Clear Logs
  2. Reduce refresh intervals:
    • Settings → Background Tasks
    • Increase refresh interval (default: 5 minutes)
    • Disable auto-refresh if not needed
  3. Limit active accounts:
    • Disable accounts you’re not actively using
    • The token manager caches quota in memory for performance
  4. Disable smart warmup:
    • Settings → Smart Warmup
    • Toggle off if you don’t need preemptive quota checking
Symptoms:
  • Container exits immediately
  • “API_KEY not set” error
  • Cannot access web interface
Solutions:
  1. Check environment variables:
  2. Ensure API_KEY is set:
  3. Check volume permissions:
  4. Verify port availability:
  5. Access the web interface:
    • Navigate to http://localhost:8045
    • Login with your API_KEY or WEB_PASSWORD

Update Issues

Solutions:
  1. Check internet connection and proxy settings:
    • Settings → Global Upstream Proxy
    • Ensure proxy allows access to GitHub
  2. Manual update:
  3. For Homebrew users:
  4. Check update logs:
    • Look for error messages in ~/.antigravity_tools/logs/app.log
    • Search for “update” or “download” keywords

Integration Issues

Symptoms:
  • claude command cannot connect
  • Authentication errors
  • Model not found errors
Solutions:
  1. Verify environment variables:
  2. Check if proxy is running:
    • Ensure Antigravity Manager is open
    • Verify API Proxy is enabled
  3. Test the connection:
Solutions:
  1. Verify OpenCode is installed:
  2. Check custom base URL:
    • Settings → External Providers → OpenCode
    • For Docker: set Custom Manager BaseURL to your Docker host
  3. Manual configuration:
    • Locate ~/.config/opencode/opencode.json
    • Add the antigravity-manager provider manually
  4. Restore from backup:
    • If sync corrupts config, restore from .antigravity.bak

Next Steps