Open-source project
yuaotian/antigravity-proxy avatar
yuaotian/antigravity-proxy

Antigravity-Proxy: a version.dll injector that sends Antigravity traffic through SOCKS5 or HTTP without TUN

Transparent proxy injector for Antigravity. Forces SOCKS5/HTTP proxy without TUN mode on Windows, using DLL injection and process traffic hijacking.

4,880 stars342 forksC++NOASSERTION

At a glance

What is it?
Antigravity-Proxy is a Windows DLL for the Antigravity editor and CLI that hijacks the traffic of selected processes and sends it to a local SOCKS5 or HTTP proxy, with no Clash TUN mode and no administrator rights. It cannot fix an exit IP that Antigravity's servers reject, and that is the failure its author warns about first.
Who is it for?
Use it on Windows if Antigravity ignores your system proxy and you want only its processes proxied rather than the whole machine. It will not help when the exit IP itself is refused, and it asks you to place DLLs beside the application and run a bundled runtime installer, so check the LICENSE.txt terms and the origin of every binary first.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • yuaotian/antigravity-proxy4,880 ★ · +607
Star history
Repository2026-09-282026-11-15
yuaotian/antigravity-proxy4.3k4.9k

607 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

A 'User location is not supported' error comes from the exit IP, and the DLL cannot change that

The project opens with a warning placed above its own introduction. If the Antigravity chat shows `Agent execution terminated due to error`, check the proxy's exit IP before suspecting the DLL. The author describes a confusing situation seen in practice: version.dll is loaded, language_server_windows_x64.exe and node.exe are both injected, oauth2.googleapis.com and daily-cloudcode-pa.googleapis.com connect through SOCKS5, and yet Antigravity's own ls-main.log still reports `FAILED_PRECONDITION (code 400): User location is not supported for the API use.`

The explanation given is that the country, ASN or data-centre character of the exit address is judged unusable by the agent execution path, so a supported country does not guarantee that this particular exit is accepted. The suggested order is to read the DLL log first, then ls-main.log, then switch to a non-data-centre, ordinary ISP or residential exit and retry. Two exits in the same country, for example Singapore, can behave differently.

The consequence is plain: the tool moves traffic, and it has no control over the verdict the server returns. If the DLL log shows successful injection and SOCKS5 tunnels, swapping DLL versions will not clear a location error.

Two logs tell you whether the injection worked or the server refused you

The DLL writes its own log to `<Antigravity install directory>\logs\proxy-YYYYMMDD.log`. Lines to look for are the injection successes for language_server_windows_x64.exe and node.exe, and SOCKS5 tunnel established lines naming oauth2.googleapis.com:443 and daily-cloudcode-pa.googleapis.com:443. If those exist, the DLL is doing its job.

The second log belongs to the application: `%APPDATA%\Antigravity\logs\<latest timestamp folder>\ls-main.log`. An `agent executor error` with the location message there means the failure is on the agent side.

For a deeper check, the configuration page has a switch named `diagnostics.agent_ip_probe`. With it on, the DLL adds IP diagnostic lines: one when the exit probe completes, one when the exit looks like a data-centre or hosting address, and one when the newest Antigravity log has already hit the location error while the exit also looks like hosting. Those lines turn a vague chat error into a specific cause. Only when the DLL log shows no successful injection or no proxy handshake does the project send you back to debugging the DLL.

The IDE and the CLI each load a different DLL name, and mixing them breaks the setup

Interception works by planting a DLL that the host process loads. For the desktop editor, that is `version.dll` plus `config.json`, copied next to Antigravity.exe. For the Antigravity CLI, it is `dbghelp.dll`, `antigravity_proxy.dll` and `config.json`, copied next to agy.exe. The CLI uses two files because dbghelp.dll loads a uniquely named antigravity_proxy.dll on the first call to an exported function, which avoids a name clash with the system version.dll.

Releases ship as four archives named like `antigravity-proxy-vX-ide-win-x64.zip` and `...-x86.zip` for the IDE, and the matching `cli` pair. Each also contains `config-web.html` and a usage guide. Self-built output lands in `output/ide` and `output/cli`.

Three rules follow from this. Do not copy the ide and cli folders together, and the desktop build does not need dbghelp.dll. The version.dll and config.json must come from the same build and the same architecture. In Antigravity 2.0, if the application can start from several directories, the files have to go into the directory it really launches from. A healthy start shows a log line announcing full mode, after which you can verify OAuth callbacks and business requests in the logs.

Only the processes in target_processes are proxied, and Antigravity 2.0 renamed some of them

The tool does not take over the whole machine. It proxies the processes named in `config.json`, and children are covered when `child_injection` is true. Antigravity 2.0 added or renamed key processes, and the default configuration already lists them:

json
"target_processes": [
  "agy.exe",
  "language_server.exe",
  "language_server_windows",
  "Antigravity.exe",
  "Antigravity IDE.exe",
  "node.exe"
]

If you migrate an old `config.json` by hand, confirm that `child_injection` is still true and copy this list in. A stale list is the quiet failure here: the editor window starts, but a renamed helper process goes out directly and never uses the proxy.

The flip side is the advertised benefit. Because only Antigravity processes are redirected, other local development traffic stays untouched, which is the stated reason for avoiding TUN mode, where all traffic is proxied and administrator rights may be needed. The comparison table in the project says this tool works for a normal user and that you put the DLL in place and it works.

The proxy port has to match your client, and SOCKS5 is the supported path

The quick start assumes a SOCKS5 or HTTP proxy already listens on your machine, such as `127.0.0.1:7890`. The project provides a table of default ports. Clash, Clash Verge, Clash for Windows and Mihomo use 7891 for SOCKS5 and 7890 for HTTP, with 7890 also serving as a mixed port. V2RayN uses 10808 and 10809. V2RayA uses 20170 and 20171. Shadowsocks and ShadowsocksR give SOCKS5 on 1080 and no HTTP. NekoBox uses 2080 and 2081, and sing-box has no default because the port comes from your own configuration.

The project recommends SOCKS5, saying its support there is more complete than for HTTP. That matters for a Shadowsocks setup, where SOCKS5 is the only option anyway.

Before blaming the DLL, confirm the port is open. In PowerShell:

powershell
Test-NetConnection -ComputerName 127.0.0.1 -Port 7891

The same table lists three common causes: a port taken by another program, found with `netstat -ano | findstr :7890`, a proxy client that is not running, and a Windows firewall block. Surge's enhanced mode can use different ports, so read the actual value from the client's own settings.

Error 0xc0000142 points to missing runtimes, and the fix is an executable stored in the repository

If the target program fails to start with error code 0xc0000142, the project attributes it to missing Windows runtime libraries. Its remedy is a bundled installer: `microsoft\微软常用运行库合集-2025.exe`, a Chinese-named runtime collection in the repository's microsoft folder. The steps are to open that folder, run the installer, finish the wizard and restart the target program.

That advice has a cost. You are asked to run a prebuilt third-party executable fetched from a GitHub repository, not from the vendor of the libraries. Check where it came from before you run it, since the project only documents its own route.

A second caution comes from the nature of the tool itself. A DLL that is loaded by an application, hooks its network calls and injects into child processes, including node.exe, is invasive software. Run it only on a machine where you accept that, and keep the archives from the official releases page, not from reposts.

Windows-only by design, with no support promised for the exit IP, and a license field GitHub could not classify

Everything above is Windows machinery: version.dll, dbghelp.dll, x64 and x86 builds, a CMake project with a `build.ps1` script, and a PowerShell diagnostics flow. The project table of contents also lists a WSL guide, but the injection itself targets Windows builds of Antigravity.

Releases are recent. v2.2 came out on 2026-06-19, v2.3 on 2026-08-31 and v2.4 on 2026-09-01, the same day as the last push, so the code has moved within the last few months. The repository carries tests, docs, scripts and tools directories next to the source.

The license field is NOASSERTION, which means GitHub did not identify a standard license. The README links to LICENSE.txt in the repository, so read that file for the actual terms before redistributing or modifying the DLL.

Who is this for? Someone on Windows who wants Antigravity's own traffic proxied without enabling TUN mode. Who is it not for? Anyone hoping it will make an unsupported exit IP acceptable, or anyone who cannot place DLLs beside the application.

Editorial conclusion

Use it on Windows if Antigravity ignores your system proxy and you want only its processes proxied rather than the whole machine. It will not help when the exit IP itself is refused, and it asks you to place DLLs beside the application and run a bundled runtime installer, so check the LICENSE.txt terms and the origin of every binary first.

Frequently asked questions

What is an Antigravity proxy in the Antigravity-Proxy project?

It is a Windows DLL injected into the Antigravity editor or CLI that forces the traffic of selected processes into a SOCKS5 or HTTP proxy. It works without Clash TUN mode and does not take over all traffic on the machine.

How to use Antigravity-Proxy?

Start a SOCKS5 or HTTP proxy such as 127.0.0.1:7890, download the matching ide or cli archive, and copy its files next to Antigravity.exe or agy.exe. The version.dll and config.json must come from the same build and architecture.

Can you access Antigravity remotely with Antigravity-Proxy?

It is not a remote-access tool. It routes Antigravity processes on your own Windows machine through a proxy, and a rejected exit IP still returns a location error from Antigravity.

Official sources

  1. Issues
  2. README
  3. Releases
  4. yuaotian/antigravity-proxy on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/yuaotian-antigravity-proxy.svg)](https://hysenlabs.com/projects/yuaotian-antigravity-proxy)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/yuaotian-antigravity-proxy.svg)](https://hysenlabs.com/projects/yuaotian-antigravity-proxy)

Was this useful?