OFFICIAL TROUBLESHOOTING KNOWLEDGE BASE

Fix Google Antigravity Errors & Region Lock

Complete step-by-step solutions for Error 403 Forbidden, 429 Quota Exhaustion, Middlebox TLS Resets, and No-TUN Smart Proxy setup.

1-Click Universal Auto-Fix (Recommended)

Instead of manually editing JavaScript bundles and configuring network routing, run Antigravity Cleaner to patch all 4 targets and generate an isolated proxy launcher automatically:

curl -sSL https://raw.githubusercontent.com/tawroot/antigravity-cleaner/main/install.sh | bash && ag-cleaner patch

* On Windows: Open PowerShell and run irm https://raw.githubusercontent.com/tawroot/antigravity-cleaner/main/install.ps1 | iex

ERROR 403 FORBIDDEN • REGION LOCK

"Service is not available in your country" / Region Lockout

Root Cause: Google DeepMind and Google Cloud enforce strict geographic restrictions on Google Antigravity in countries such as Iran, Russia, China, Cuba, and Syria. The IDE runs internal JavaScript gatekeeper functions that inspect telemetry and token responses. If blocked, Antigravity forces a session invalidation and kicks you out to the login screen.

HTTP 403 Forbidden: Your region is not eligible for Google Antigravity developer preview.

Fixing Error 403 Step-by-Step:

  1. Neutralize Client-Side Checks: Run antigravity-cleaner patch. This surgically unlocks main.js, the IDE binary, CLI (agy), and VS Code extension so the software never locks itself.
  2. Launch with Smart Proxy (No TUN): Run antigravity-cleaner launch. This passes --proxy-server=socks5://127.0.0.1:10808 directly to the Chromium engine. Chromium will resolve Google auth endpoints through your foreign proxy IP, keeping your session intact.
  3. Avoid TUN Mode: Never use global TUN mode for Antigravity. TUN mode causes MTU packet fragmentation and triggers Middlebox DPI dropouts.
ERROR 429 • RATE LIMIT / QUOTA EXHAUSTED

"Too Many Requests" & Corrupted Token Cache

Root Cause: Autonomous agents generate dozens of tool calls, search queries, and subagent transcripts per session. Local token buckets in ~/.config/Antigravity/Cache and DawnWebGPUCache get out of sync with Google's servers, causing perpetual 429 errors even when you have quota left.

Error 429: Resource has been exhausted (e.g. check quota).

How to Resolve Error 429 without Losing Data:

  1. Click the [Reset 429] button in the Antigravity Cleaner GUI or run:
    antigravity-cleaner clean
  2. Session Preservation Guarantee: Our surgical reset purges corrupted quota blobs and telemetry caches while strictly preserving your Cookies, Preferences, app_storage.json, and chat history. You do NOT have to log in again.
NETWORK ARCHITECTURE • NO-TUN MODE

Smart Proxy Injection for v2ray, Xray, Clash, and NekoBox

Why traditional VPNs fail: When you enable TUN mode, your entire operating system's traffic is redirected through the VPN. This increases latency, causes packet drops, and breaks local intranet and domestic banking websites.

How Antigravity Cleaner's No-TUN Injection Works:

  1. The Cleaner automatically scans local loopback ports:
    • 127.0.0.1:10808 (v2ray / Xray SOCKS5)
    • 127.0.0.1:2080 (NekoBox / Hiddify SOCKS5)
    • 127.0.0.1:7890 (Clash / Mihomo Mixed)
    • 127.0.0.1:1080 (Standard SOCKS5)
  2. It launches Antigravity with a dedicated pipeline: --proxy-server=socks5://127.0.0.1:.
  3. Only Google Antigravity traffic is routed through the proxy. Your web browser, terminal downloads, and domestic sites continue running at maximum local speed!
antigravity-cleaner create-launcher

This generates a permanent 1-click desktop launcher (Antigravity.desktop on Linux, Antigravity.lnk on Windows, Antigravity-Proxy.command on macOS).

CONNECTION DROPOUT • MIDDLEBOX DPI

Middlebox TLS Disconnects & Stream Interruptions

The Issue: During deep thinking or multi-minute code planning, the HTTP/2 SSE connection between the IDE and Google's edge server (daily-cloudcode-pa.googleapis.com) remains silent. Strict ISP firewalls (Middleboxes) mistake idle TLS connections for dead tunnels and send TCP RST packets, causing "Stream Closed / Broken Pipe" errors.

The Solution:

Antigravity Cleaner patches the socket connection layer to inject a 15-second TCP KeepAlive heartbeat. This keeps the stateful connection alive across all firewalls and middleboxes without dropping your agentic sessions.

STARTUP FAILURE • SINGLETON LOCK

Antigravity Won't Open After Crash or Sleep

The Issue: If your system suspends or Antigravity crashes, Chromium leaves a lockfile at ~/.config/Antigravity/SingletonLock pointing to a dead PID. When clicked, Antigravity thinks another instance is active and refuses to open.

# Manual fix: rm -f ~/.config/Antigravity/SingletonLock ~/.config/Antigravity/SingletonSocket ~/.config/Antigravity/SingletonCookie

Antigravity Cleaner's smart launcher audits and removes stale singleton locks automatically on every launch!