Repository navigation
Troubleshooting Guide
This guide provides definitive troubleshooting procedures for common Antigravity IDE and network errors.
When sending any prompt (even a basic "Hello"), the IDE returns:
You do not have a valid license of this product. Please contact your administrator to request a license... (#3501)
The core language_server binary was not found in the standard candidate paths during initial patching, or Antigravity was updated and reverted the machine-code patch. Running ag-cleaner doctor displays:
Core Engine CHECK Not Found
- Locate your Antigravity binary installation:
-
Linux:
find ~ /opt /usr -name "language_server" 2>/dev/null
-
macOS:
find /Applications ~/Applications -name "language_server" 2>/dev/null
-
Windows (PowerShell):
Get-ChildItem -Path "$env:LOCALAPPDATA\Programs" -Filter "language_server.exe" -Recurse
-
Linux:
- Manually patch using the direct path:
ag-cleaner patch core /path/to/resources/bin/language_server
- Restart Antigravity using
ag-cleaner launch.
Model requests fail with HTTP 429 or "Quota Exceeded" even when your quota should be intact.
Perform a surgical state reset. This clears corrupted token caches and network state cookies while strictly preserving all conversation trajectories and workspace settings:
echo "y" | ag-cleaner cleanAI response streaming suddenly halts midway through a turn, displaying The stream was interrupted. Please continue the task you were working on.
Stateful firewall middleboxes and Deep Packet Inspection (DPI) systems silently drop idle TCP connections on Server-Sent Event (SSE) streams if no packets transit for a few seconds.
- Always launch Antigravity using the smart launcher:
Or generate the permanent desktop shortcut:
ag-cleaner launch
ag-cleaner create-launcher
- Ensure your proxy node has low packet-loss (< 1%) and an exit latency under 1500ms to Google edge services (
daily-cloudcode-pa.googleapis.com).
Transient proxy tunnel reconnects or local DNS leakage caused the request to reach Google endpoints with an unsupported or flagged data center IP.
- Verify DNS uses remote resolution by confirming your environment specifies
socks5h://:export ALL_PROXY="socks5h://127.0.0.1:10808" export HTTPS_PROXY="socks5h://127.0.0.1:10808"
- Switch to a residential or clean European data center node (Germany, Netherlands, Finland) in your proxy client.