Knowledge Base & Security

Frequently Asked Questions

Detailed answers on Error 403 region bypass, Error 429 quota recovery, No-TUN proxy architecture, and security assurances.

Bypass • Error 403

Q: How do I fix Google Antigravity Error 403 Forbidden: Region Lock?

Google Antigravity enforces client-side eligibility checks in main.js, the agy CLI daemon, and internal extensions alongside server-side Geo-IP verification. When an unsanctioned country (such as Iran, Russia, or China) is detected, Antigravity forces a session invalidation.

Solution: Run antigravity-cleaner patch all (or click [Auto-Fix] in the GUI). This surgically neutralizes client-side region gates across all 4 software targets. Then launch with antigravity-cleaner launch to route the IDE through your local loopback proxy without TUN mode.

Recovery • Error 429

Q: How to resolve Error 429 Quota Exceeded without losing chat history?

Corrupted local token buckets and rate-limit cache files in ~/.config/Antigravity/Cache and DawnWebGPUCache frequently freeze the client runtime in a perpetual 429 state even after quota should have refreshed.

Solution: Run antigravity-cleaner clean (or click [Reset 429] in GUI). Our surgical reset purges only 16 corrupted telemetry and rate-limit files in 0.002s while strictly preserving 100% of your Google login cookies, project context, and chat history.

Network • No-TUN

Q: Why does Antigravity Cleaner avoid TUN mode?

Enabling TUN mode creates a virtual network interface that captures all device network traffic. This causes MTU packet fragmentation, slows down terminal package downloads (npm, pip, docker), breaks local developer servers (localhost:3000), and breaks domestic banking or intranet sites.

Antigravity Cleaner uses Process-Level Injection (--proxy-server=socks5://127.0.0.1:<port>). Only the IDE traffic routes through your proxy, while the rest of your operating system enjoys direct high-speed internet.

Security • Offline

Q: Is Antigravity Cleaner safe, open-source, and private?

Yes, 100%. Antigravity Cleaner is released under the permissive Apache 2.0 license. It runs completely offline on your local loopback address (127.0.0.1), contains zero external telemetry, zero phoning home, and has passed automated security audits with GitHub CodeQL and Govulncheck.

It never reads, transmits, or alters your private code repositories or personal API tokens.

Crash Fix • write EIO

Q: How to fix "Agent terminated due to error" (write EIO broken pipe)?

This crash happens when verbose console and telemetry logging fills the Node.js IPC pipe, or when state firewalls drop silent streaming inference connections while the AI model is performing deep multi-step thought planning.

Solution: Run antigravity-cleaner patch all. Our Zero-Log ASAR Shield silences raw stdout/stderr write pipes, intercepts broken stream exceptions gracefully, and enforces an aggressive 15-second TCP KeepAlive socket heartbeat to maintain active edge server connectivity.

Proxy • Connection Refused

Q: How to fix "proxyconnect tcp: dial tcp 127.0.0.1:10808: connect: connection refused"?

This error indicates that the IDE is trying to connect to a local proxy on port 10808 (v2ray/Xray default), but your proxy client is either closed or listening on a different port (such as 7890 for Clash, 2080 for NekoBox, or 1080 for generic SOCKS).

Solution: Run antigravity-cleaner doctor. The diagnostic engine dynamically scans all active loopback sockets, detects your running proxy port, and aligns your IDE proxy configuration automatically.

State Fix • Failed to Fetch

Q: How to fix "There was an unexpected issue setting up your account. Failed to fetch"?

This error stems from corrupted DIPS database records and orphaned WebSocket caches in Electron application state, which blocks the initial onboarding handshake.

Solution: Execute antigravity-cleaner clean. It resets corrupted session caches in under 0.01s while leaving your saved login tokens and chat archives completely intact.

Startup Lock • SingletonLock

Q: Antigravity won't open after crash or system sleep. How to fix it?

When Chromium is terminated abruptly or the system suspends, an orphaned lockfile at ~/.config/Antigravity/SingletonLock is left pointing to a dead PID. Subsequent launches detect the lockfile, assume an instance is already running, and exit silently.

Solution: Launching via antigravity-cleaner launch automatically audits and purges stale singleton lockfiles before opening the IDE every time!

Maintenance • Ubuntu Linux

Q: How do I completely clear Antigravity IDE cache or uninstall on Ubuntu?

To clear cache safely: Run ag-cleaner clean (clears temporary GPU and quota blobs without logging you out). For a full factory reset, run ag-cleaner clean --deep.

To completely uninstall on Ubuntu:

sudo dpkg -r antigravity || sudo apt-get remove antigravity

rm -rf ~/.config/Antigravity ~/.antigravity ~/.local/share/applications/Antigravity*.desktop

Compatibility • macOS & Linux

Q: Do you support Apple Silicon (M1/M2/M3/M4) Macs and Linux?

Yes. Antigravity Cleaner provides native standalone executables for macOS Apple Silicon (ARM64) and Intel (x86_64), Linux (Debian, Ubuntu, Fedora, Arch), and Windows 10/11.

Maintenance • Atomic Backup

Q: Can I restore the original files if Google releases an official IDE update?

Yes. Every time a patch is applied, Antigravity Cleaner generates an atomic .agybak backup snapshot of the original files. Simply run antigravity-cleaner restore (or click [Restore] in GUI) to instantly revert all binaries and JavaScript files to their pristine original state.

Architecture • Comparison

Q: How does Antigravity Cleaner differ from Python patchers like open-antigravity-patcher or QNIX?

Unlike single-purpose Python scripts that only modify one file and require Python runtimes, Antigravity Cleaner is compiled in native Go with zero dependencies. It provides a complete diagnostic doctor engine, a Retro KeyGen GUI with 8-bit sound, automatic proxy port discovery, atomic backup/restore, desktop launcher generator, and surgical quota reset.