confeden/Antigravity

Adoption takeaway: consider this only if you specifically need Antigravity while signed in with an account from a restricted region and accept a closed-source unlock flow with a Telegram-delivered key.

The problem

A developer in, say, Russia installs Google's Antigravity 2.0, IDE or CLI, signs in with their ordinary Google account, and hits a regional refusal such as the documented "User location is not supported" error. Today the usual workaround would be a VPN and possibly an account region change, which affects the whole machine or account rather than one tool. Antigravity changes that last step: a local helper patches the installed client and routes only two Google endpoints through a local service, so the user can keep their account and network setup. The author reports that the in-app status card turns green once a model reply succeeds.

What's different

This is a client-side patcher plus a small local proxy, not a general VPN review. The README says it rewrites two equal-length strings inside language_server.exe and agy.exe (ineligible → inexigible) so the file size stays the same, then points only a renamed AG_LS_PROXY variable at a service on 127.0.0.1:53129. It also adds DNS rules for two cloudcode-pa.googleapis.com hosts and may prioritize IPv4 when no global IPv6 exists. Because the system HTTPS_PROXY, TLS interception and certificates are left alone, Git and browsers are meant to behave as before; the README also says path selection follows which route actually answered the model, not raw speed.

The trade-off is that this depends on the installed binary's exact contents. Antigravity is described as re-patching after an update, and a key is version-specific, so each unlocker release needs a fresh key from the project's Telegram group. The README admits that built-in exits and the server side of the group-proxy route are not in the open source, so the published code cannot be fully audited and the service still depends on a closed component and a community-delivered key. The authors also advise running binaries in a VM if you distrust them; that is a caution about antivirus reactions, not a safety guarantee.

Who should try it

It fits a developer who already wants to use Antigravity's editor or CLI from a restricted region and is willing to run an unsigned helper as administrator on Windows or via pkexec on Linux. A Linux archive with launch.sh avoids sudo for the ordinary case, and the TUI script covers SSH servers, so headless setups have documented paths too. It does not fit someone who needs an auditable, fully open tool for production engineering, or who wants Gemini CLI support: the README states Google closed personal-account login there and the project does not support it.

Requirements and limitations

On Windows, the README says the full path needs administrator rights; otherwise only the client patch is applied and the error-400 service is left out. A valid, version-specific key is mandatory and changes with unlocker updates, so access is not self-contained. Linux users typically do not need sudo, but the patcher requests elevation through pkexec when Antigravity lives under /opt. The project changes system-level DNS rules (NRPT) and possibly IPv4 preference, and rollback is done by toggling switches; treat that as an operational procedure to understand, not a guarantee of complete restoration. Antivirus tools may flag unsigned binaries, and the absence of the proxy server and exit list from the public source is a lasting verification gap.

HotRepo's take

HotRepo recorded +423 stars on the monthly Rust board, rank #20, on 2026-10-26. That is one dated snapshot with no comparable daily history, so persistence of interest cannot be judged from it. Before spending time, verify that a release and key exist for your exact Antigravity build and that the documented re-patch behavior matches your update cycle.

Project source and documentation