Antigravity-Proxy

🚀 Built for the Antigravity editor: use proxy without TUN mode (especially useful in China)

🇨🇳 中文版

📖 Table of Contents

• 📖 Introduction
• 🚨 Read This First: Check IP Before DLL
• ⚡ Antigravity Quick Start
• 🔧 Troubleshooting Guide
• ✨ Features
• 🔧 How It Works
• 🛠️ Build
• 📝 Usage
• 🚀 Advanced Usage
• 📄 License
• 👤 Author

🚨 Read This First: Check IP Before DLL

If Antigravity shows Agent execution terminated due to error, check your proxy egress IP first. Do not assume the DLL stopped working.

We have already verified the most misleading real-world scenario:

• version.dll is loaded successfully
• language_server_windows_x64.exe is injected successfully
• node.exe is injected successfully
• oauth2.googleapis.com / daily-cloudcode-pa.googleapis.com are still reachable through SOCKS5
• but Antigravity's own ls-main.log still returns:
  • FAILED_PRECONDITION (code 400): User location is not supported for the API use.

In cases like this, the main cause is usually not DLL failure. It is more often:

• the current proxy egress IP / ASN / datacenter characteristic being rejected by Antigravity agent mode / Gemini CLI path
• in other words: a supported country does not guarantee that this exact agent execution path accepts the current egress IP

Which two logs should you check first

1. DLL log: proves the injection layer is alive

• <Antigravity Install Dir>\\logs\\proxy-YYYYMMDD.log

If you can see lines like these, the DLL itself is already doing its job:

• [成功] 已注入目标进程: language_server_windows_x64.exe
• [成功] 已注入目标进程: node.exe
• SOCKS5: 隧道建立成功, 目标=oauth2.googleapis.com:443
• SOCKS5: 隧道建立成功, 目标=daily-cloudcode-pa.googleapis.com:443

Starting from this version, the DLL also emits IP diagnostics:

• [诊断/IP] 当前代理出口探测完成: ...
• [诊断/IP] 当前代理出口呈现机房/托管特征...
• [诊断/IP] 最新 Antigravity 日志已命中 location 限制错误，同时当前代理出口呈现机房/托管特征...

2. Antigravity app log: proves the real failure is inside agent execution

• %APPDATA%\\Antigravity\\logs\\<latest session>\\ls-main.log

If you see this line:

• agent executor error: FAILED_PRECONDITION (code 400): User location is not supported for the API use.

then the real meaning is:

• the failure is no longer in DLL injection or the basic proxy tunnel
• the failure is now inside Antigravity's own agent execution path

Most effective troubleshooting order

1. Check proxy-YYYYMMDD.log
   • If injection and SOCKS5 are both successful, the DLL is probably fine.
2. Check %APPDATA%\\Antigravity\\logs\\<latest session>\\ls-main.log
   • If it contains User location is not supported for the API use., prioritize IP troubleshooting.
3. Try a non-datacenter / non-hosted / residential / normal ISP egress IP first
   • Even inside the same country (for example, Singapore), different ASN / different egress types can lead to completely different results.
4. Only go back to DLL troubleshooting if the DLL log does not show successful injection or successful proxy tunnel creation.

One-line memory hook

When Antigravity chat fails, check the egress IP before blaming the DLL. If you see location is not supported, prioritize IP first.

⚠️ Environment Requirements

Before using this tool, ensure the required runtime libraries are installed, otherwise the target application may fail to start.

Common Issue: Error 0xc0000142

If you encounter error code 0xc0000142 when launching the program (as shown below), it's usually caused by missing Windows runtime libraries.

Solution

Please install the Microsoft Visual C++ Runtime Pack, which is included in this repository:

📦 Download Path: microsoft\微软常用运行库合集-2025.exe

Installation Steps:

1. Navigate to the microsoft folder in this repository
2. Run 微软常用运行库合集-2025.exe
3. Follow the installation wizard
4. Restart the target application

📖 Introduction

Antigravity-Proxy is a Windows proxy injection module built specifically for the Antigravity editor.

The goal is simple: help users (especially in China) use Antigravity without enabling Clash TUN mode, while still sending Antigravity’s traffic through your SOCKS5/HTTP proxy.

Name note: Antigravity-Proxy = Antigravity + Proxy — it pulls only Antigravity-related processes into the proxy (not a global system takeover).

🎯 Problem Solved

Have you ever encountered these situations?

• 🔴 Antigravity doesn't respect system proxy in some environments, forcing you to enable Clash TUN mode
• 🔴 TUN mode proxies all traffic globally, affecting local development
• 🔴 TUN mode requires administrator privileges, which some environments don't allow

Antigravity-Proxy comes to the rescue! It can:

• ✅ Proxy only specified applications (primarily Antigravity-related), without affecting other traffic
• ✅ No TUN mode required, avoiding a global proxy takeover
• ✅ Transparent proxy, target applications are completely unaware

🌟 Core Value

⚡ Antigravity Quick Start

If you only care about getting Antigravity working right now, this is the shortest path.

Step 1: Prepare a Proxy

Start your proxy client (e.g. Clash/Mihomo) and make sure you have a local SOCKS5 or HTTP proxy endpoint (e.g. 127.0.0.1:7890).

# Test SOCKS5 port (default 7891)
Test-NetConnection -ComputerName 127.0.0.1 -Port 7891

# Test HTTP port (default 7890)
Test-NetConnection -ComputerName 127.0.0.1 -Port 7890

# Test via SOCKS5 proxy
curl -x socks5://127.0.0.1:7891 https://www.google.com -I

# Test via HTTP proxy
curl -x http://127.0.0.1:7890 https://www.google.com -I

Step 2: Get the Files

You need these files:

• version.dll
• dbghelp.dll (Antigravity CLI only)
• config.json

(Download from Releases, or build them yourself.)

Step 3: Deploy to Antigravity

Copy version.dll and config.json to Antigravity’s main program directory (next to Antigravity.exe). Then launch Antigravity — done.

For Antigravity CLI, copy dbghelp.dll, version.dll, and config.json next to agy.exe. agy.exe loads the colocated dbghelp.dll, which then loads version.dll; no separate launcher is required.

Antigravity 2.0 Notes

Antigravity 2.0 added/renamed key processes. The default config now covers:

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

If you are migrating an old config.json, make sure child_injection is still true and sync the target process list above. If your 2.0 install has more than one launch directory, place version.dll and config.json in the actual Antigravity/IDE directory being launched.

Antigravity updates may clean injected files from the install directory. If proxying stops after an update, copy the files again. If your proxy client separates mixed-port and SOCKS5 ports, make sure proxy.type and proxy.port match the actual local listener.

More field notes: docs/antigravity-2.0-issue-85.md.

Common Windows Path + Quick Jump

In most cases, Antigravity is installed at:

C:\Users\<username>\AppData\Local\Programs\Antigravity\

Example: C:\Users\yuaotian\AppData\Local\Programs\Antigravity

If you can’t find the folder: locate the Antigravity shortcut (Desktop/Start Menu), right-click → Open file location — that folder is Antigravity’s main directory.

Quick jump from terminal:

cd "$env:LOCALAPPDATA\Programs\Antigravity"

cd /d "%LOCALAPPDATA%\Programs\Antigravity"

(Optional) Set a custom env var so you can jump there anytime:

setx ANTIGRAVITY_HOME "%LOCALAPPDATA%\Programs\Antigravity"

After that: PowerShell cd $env:ANTIGRAVITY_HOME, CMD cd /d %ANTIGRAVITY_HOME%.

🔧 Troubleshooting Guide

Proxy not working? Follow this guide to diagnose and fix the issue.

📋 Quick Diagnostic Flowchart

Proxy not working?
    │
    ├── Check if log file exists ─────────────────────────────────┐
    │       │                                               │
    │       ├── ❌ No log → DLL not loaded / wrong location    │
    │       │       └── See "DLL Loading Issues"              │
    │       │                                               │
    │       └── ✅ Has log → Check log contents              │
    │               │                                       │
    ├── Does log contain "SOCKS5: Tunnel established"? ──────┤
    │       │                                               │
    │       ├── ❌ No → Proxy connection failed              │
    │       │       └── See "Proxy Software Check"           │
    │       │                                               │
    │       └── ✅ Yes → Tunnel ok, issue is downstream      │
    │               │                                       │
    └── Check Clash logs and node availability ───────────────┘

🔍 Step 1: Check Log Files

Logs are your first source of debugging information.

Log Locations (by priority):

1. <Antigravity Install Dir>\logs\proxy-YYYYMMDD.log
2. %TEMP%\antigravity-proxy-logs\proxy-YYYYMMDD.log

Quick Access:

# Open logs folder in DLL directory
cd "$env:LOCALAPPDATA\Programs\Antigravity\logs"

# Or open TEMP directory
cd "$env:TEMP\antigravity-proxy-logs"

Key Log Lines Explained:

🌐 Step 2: Proxy Software Check

2.1 Verify Proxy Port is Open

# Test SOCKS5/mixed port
Test-NetConnection -ComputerName 127.0.0.1 -Port 7890

# If TcpTestSucceeded: False, port is not listening

2.2 Verify Clash Configuration

Check in Clash config file:

# Must enable mixed or SOCKS5 port
mixed-port: 7890     # Mixed port (recommended)
# Or
port: 7890           # HTTP port
socks-port: 7891     # SOCKS5 port

# If LAN access is needed
allow-lan: true

2.3 Check Clash Logs

In Clash UI, check "Logs" to confirm:

• Requests from daily-cloudcode-pa.googleapis.com, www.googleapis.com
• Whether requests go DIRECT or through proxy node
• Whether any REJECT rules matched

2.4 Test Node Availability

Simplest method: Enable TUN mode. If Antigravity works in TUN mode, your proxy node is fine.

💻 Step 3: System Environment Check

3.1 Check Windows Version

winver

Different Windows 11 builds may have different Winsock behaviors.

3.2 Check Winsock LSP Configuration

Some security software injects LSP (Layered Service Providers), which may interfere with hooks.

# Run as Administrator
netsh winsock show catalog

Normally you should only see Microsoft providers. Third-party providers (from 360, Huorong, etc.) may cause compatibility issues.

3.3 Check Security Software

These may interfere with DLL injection or hooks:

Troubleshooting tip: Try completely exiting security software (not just minimizing to tray).

3.4 Check IPv6 Configuration

If IPv6 is enabled, some connections may prefer IPv6:

# Check network adapter IPv6 status
Get-NetAdapterBinding -ComponentID ms_tcpip6

If logs show many IPv6-related entries, try setting in config.json:

"proxy_rules": {
    "ipv6_mode": "block"
}

🔄 Step 4: Comparison Check

If your environment works but a friend's doesn't, compare these:

📊 Step 5: Collect Info for GitHub Issue

If the above steps don't resolve your issue, collect this info and submit a GitHub Issue:

1. Log file: Complete proxy-YYYYMMDD.log contents
2. config.json: Your config file (hide sensitive info)
3. Windows version: winver output
4. Clash version and config (port settings)
5. Security software list: Installed antivirus/security software
6. Problem description: What exactly doesn't work? What site/feature fails?

⚠️ Known Compatibility Issues

✨ Features

Supported Protocols

• ✅ SOCKS5 (Recommended)
• ✅ HTTP CONNECT

🔧 How It Works

Architecture

┌─────────────────────────────────────────────────────────────────────────┐
│                           Target Process                                 │
│  ┌──────────────┐    ┌──────────────┐    ┌──────────────────────────┐   │
│  │  App Code    │───►│ Winsock API  │───►│  antigravity-proxy.dll   │   │
│  │              │    │ (ws2_32.dll) │    │  (Hook Layer)            │   │
│  └──────────────┘    └──────────────┘    └────────────┬─────────────┘   │
│                                                       │                  │
└───────────────────────────────────────────────────────│──────────────────┘
                                                        ▼
                                              ┌──────────────────┐
                                              │   Proxy Server   │
                                              │  (SOCKS5/HTTP)   │
                                              └──────────────────┘

Core Flow

┌─────────────────────────────────────────────────────────────────────────┐
│ 1. DLL Hijacking                                                         │
│    Program loads version.dll → Loads our DLL → Forwards real calls      │
└─────────────────────────────────────────────────────────────────────────┘
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 2. Install API Hooks                                                     │
│    Uses MinHook to intercept: connect, getaddrinfo, CreateProcessW, etc │
└─────────────────────────────────────────────────────────────────────────┘
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 3. DNS Interception                                                      │
│    getaddrinfo("example.com") → Allocate FakeIP (198.18.x.x) → Save map   │
└─────────────────────────────────────────────────────────────────────────┘
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 4. Connection Redirect                                                   │
│    connect(198.18.x.x) → Lookup mapping → Connect to proxy → SOCKS5 shake │
└─────────────────────────────────────────────────────────────────────────┘
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 5. Child Process Propagation                                             │
│    CreateProcessW → Suspend process → Inject DLL → Resume                │
└─────────────────────────────────────────────────────────────────────────┘

Hooked APIs

🛠️ Build

Prerequisites

Before building, make sure you have the following tools installed:

💡 Tip: When installing Visual Studio, make sure to check the "Desktop development with C++" workload.

Dependencies

Quick Build

The project provides a PowerShell build script for one-click building:

# Default build: Release x64
.\build.ps1

# Build Debug version
.\build.ps1 -Config Debug

# Build 32-bit version
.\build.ps1 -Arch x86

# Clean and rebuild
.\build.ps1 -Clean

# Show help
.\build.ps1 -Help

Manual Build

If you prefer manual building, use these commands:

# ========== x64 (64-bit) ==========
mkdir build-x64 && cd build-x64

# Configure (using Visual Studio 2022)
cmake .. -G "Visual Studio 17 2022" -A x64

# Build Release
cmake --build . --config Release

# Output: version.dll


# ========== x86 (32-bit) ==========
mkdir build-x86 && cd build-x86

# Configure
cmake .. -G "Visual Studio 17 2022" -A Win32

# Build
cmake --build . --config Release

# Output: version.dll

Common Build Errors

# Manual download
curl -o include/nlohmann/json.hpp https://raw.githubusercontent.com/nlohmann/json/develop/single_include/nlohmann/json.hpp

target_link_libraries(version PRIVATE ws2_32)

❓ Common Errors and Error Codes

When issues occur, first confirm the target app architecture (x86/x64) and check logs (e.g. proxy-YYYYMMDD.log).

📝 Usage

Quick Start

Just 3 steps to make your target application use proxy!

Step 1: Prepare Files

After building, you'll get these files in the output directory:

• version.dll - Proxy DLL
• dbghelp.dll - Antigravity CLI shim DLL
• config.json - Configuration file

Step 2: Configure Proxy

Edit config.json:

{
    "proxy": {
        "host": "127.0.0.1",
        "port": 7890,
        "type": "socks5"
    },
    "fake_ip": {
        "enabled": true,
        "cidr": "198.18.0.0/15"
    },
    "timeout": {
        "connect": 5000,
        "send": 5000,
        "recv": 5000
    },
    "child_injection": true,
    "child_injection_mode": "filtered",
    "target_processes": [
        "agy.exe",
        "language_server.exe",
        "language_server_windows",
        "Antigravity.exe",
        "Antigravity IDE.exe",
        "node.exe"
    ]
}

Step 3: Deploy DLL

Copy version.dll and config.json to the same directory as the target application:

Target Application Directory/
├── target_app.exe
├── version.dll      ← Put here
└── config.json      ← Put here

Launch the target application, done! 🎉

Configuration Reference

Routing Rules

Routing rules live under proxy_rules.routing. They support CIDR, wildcard domains, ports, and protocol filters. Priority can be order (list order) or number (priority).

{
  "proxy_rules": {
    "routing": {
      "enabled": true,
      "priority_mode": "order",
      "default_action": "proxy",
      "use_default_private": true,
      "rules": [
        {
          "name": "lan-direct",
          "action": "direct",
          "ip_cidrs_v4": ["10.0.0.0/8","172.16.0.0/12","192.168.0.0/16"],
          "ip_cidrs_v6": ["fc00::/7","fe80::/10","::1/128"],
          "domains": [".local","*.corp.example.com"],
          "protocols": ["tcp"]
        }
      ]
    }
  }
}

Config tool: tools/config-web/index.html (open locally to import/edit/export config.json).

Note: AUTHORS.txt lists contributors of the bundled MinHook dependency, not this project’s maintainers.

Notes:

• Leave ports empty to match all ports. Leave domains empty to match CIDR only. * matches all domains.
• Use 0.0.0.0/0 and ::/0 for full match.
• The tool supports editing proxy.host / proxy.port / proxy.type.

Known Issues

• Historical (fixed): FakeIP + direct + domains + ports: In some older versions, if FakeIP is enabled and a direct rule contains both domains and ports, the DNS stage may allocate a FakeIP and the connect stage may try to connect to the FakeIP directly, causing failures. If you are on an older build, please upgrade. Temporary workaround: remove the ports condition from that rule, or disable FakeIP.

IPv6 Notes

Priority note: for pure IPv6 targets (non v4-mapped), proxy_rules.ipv6_mode takes effect before routing. Only when ipv6_mode=proxy will the connection continue into routing matching.

Verification

1. Check logs: Look for proxy.log in the target application directory
2. Check proxy software: Observe connection logs in your proxy software
3. Use packet capture: Use Wireshark to confirm traffic direction

🚀 Advanced Usage

Extra value: while this project is primarily built for Antigravity, the underlying technique is generic and can be adapted to other Windows applications that ignore system proxy.

🎯 Force Proxy Other Programs

Want Chrome, VS Code, or other programs to use proxy? Just modify the configuration!

Example 1: Force Proxy Chrome

{
    "proxy": {
        "host": "127.0.0.1",
        "port": 7890,
        "type": "socks5"
    },
    "child_injection": true,
    "target_processes": []
}

Then copy version.dll and config.json to Chrome's installation directory:

C:\Program Files\Google\Chrome\Application\
├── chrome.exe
├── version.dll      ← Put here
└── config.json      ← Put here

Example 2: Force Proxy VS Code

C:\Users\YourUsername\AppData\Local\Programs\Microsoft VS Code\
├── Code.exe
├── version.dll      ← Put here
└── config.json      ← Put here

Example 3: Proxy Only Specific Child Processes

If you only want to proxy certain child processes, use the target_processes configuration:

{
    "target_processes": [
        "node.exe",
        "npm.cmd",
        "language_server.exe"
    ]
}

🔧 Development Entry Points

If you want to do secondary development based on this project, here are the key code locations:

How to Add a New Hook?

1. Define function pointer type and Detour function in src/hooks/Hooks.cpp
2. Add MH_CreateHookApi() call in Hooks::Install()
3. Handle cleanup in Hooks::Uninstall()

How to Support a New Proxy Protocol?

1. Create new protocol implementation in src/network/ (refer to Socks5.hpp)
2. Add protocol branch in DoProxyHandshake() in src/hooks/Hooks.cpp

📄 License

This project is open-sourced under the BSD-2-Clause License.

MinHook portion is copyrighted by Tsuda Kageyu.

👤 Author

📱 Contact

🎁 Support

If this project helps you, feel free to:

• ⭐ Star this project
• 🔗 Share with friends who need it
• 💬 Submit Issues or PRs

Add WeChat

Follow Official Account

🔥 Join WeChat Group

💰 Donate

If this project helped you, consider buying the author a coffee ☕

WeChat Reward

Alipay

💳 Cryptocurrency

For international supporters, crypto donations are also welcome:

🔍 Pseudocode Source Note / 伪代码（pseudocode_dll）来源说明

The pseudocode_dll/ directory in this repository contains pseudocode obtained by decompiling a DLL published in a forum post (Binary Ninja / IDA Hex-Rays output). Its purposes are solely:

• To investigate the intermittent Antigravity crashes I encountered on Windows 11.
• To study/compare its Hook and forced proxy implementation approach.
• As a research record (for future reference).

⚠️ Important Disclaimer

• pseudocode_dll/ is NOT involved in the build or release of this project; it is merely a record of learning and research.
• The current code of this project is a version implemented from scratch and continuously maintained by me, NOT "open sourcing the original DLL".
• This repository does NOT distribute the finished DLL from the original post; please visit the original thread to obtain the original DLL.
• If the original author believes that analyzing/publishing this pseudocode is inappropriate and wishes for its removal, please file an Issue, and I will cooperate immediately (move to a separate branch/remove/rewrite description).

Source (Original Post containing DLL): https://linux.do/t/topic/1189424

Pseudocode Files in this Repo:

• pseudocode_dll/BinaryNinja.txt (Binary Ninja Decompilation Output)
• pseudocode_dll/Hex-Rays.txt (IDA Hex-Rays Decompilation Output)

_{Made with ❤️ by 煎饼果子（86）}