Core Knowledge Summary 📚

• Traditional Proxy Pain Points of AntiGravity Models and Issues with TUN Mode
• When using the Google AntiGravity IDE in the past, enabling TUN mode was mandatory. This mode proxies all system traffic, increasing local network load and making usage more complex.
• TUN is a virtual network device that routes traffic from all applications through the proxy, which can negatively impact speed and overall proxy stability.
• A new solution is introduced: Antigravity-proxy, which eliminates the need for TUN mode by using a local socket–based proxy instead.

• Overview of the AntiGravity Project Solution
• The Antigravity-proxy project works in conjunction with local proxy tools (such as v2rayN) to start local socket proxy ports (e.g., 10808 and 10809).
• By simply enabling these two socket ports, users can access Google AntiGravity models without turning on TUN mode.
• The setup is straightforward and avoids the hassle of repeatedly launching multiple complex applications.

Tutorial: Getting Started

• Downloading and Installing AntiGravity
• Visit the official Google AntiGravity website and download the 64-bit version for your operating system (approximately 152 MB).
• The installation process is explained, with a recommendation not to install the software on the C drive to avoid potential permission issues.
• Complete the installation with the default steps and get ready for the subsequent configuration.

• AntiGravity Features and Built-in Top-Tier Models
• AntiGravity is Google’s official AI IDE platform, integrating top-tier models such as Google Gemini 3, Cloud Silence 4/5, OPUS, and others.
• After registration, users can access the platform for free for a limited period, making it suitable for AI model research and practical applications.

• Preparing the Local Proxy Environment and Enabling LAN Access
• A local proxy tool such as v2rayN must be running, and the option “Allow connections from LAN” should be enabled to ensure proxy access via 127.0.0.1.
• The proxy port needs to be configured manually; in this example, port 10808 is used.
• Important note: This step is critical to ensure that the AntiGravity software can successfully connect to the local proxy.

• Downloading the Antigravity-proxy Project Files and Extracting Them

• Download the 64-bit release version from the Antigravity-proxy project page and extract it to a suitable location.

• After extraction, copy washington.dll and config.json into the same directory as the AntiGravity main executable, ensuring that the file structure is correct.

• Editing the config.json Configuration File
• Open config.json with a text editor.
• Change the proxy type to socks5 and update the default port number from 7890 to the port configured in your local proxy software (in this example, 10808 as set in v2rayN).
• Save the changes to complete the core configuration.

• Running AntiGravity and Verifying Proxy Status
• Launch the AntiGravity application and attempt to log in without enabling TUN mode. If you can log in successfully, the setup works. For confirmation, select an AntiGravity model and check whether it connects to the API through the proxy.
• Use the v2rayN logs to verify that traffic is routed through the local SOCKS proxy, ensuring the proxy is functioning correctly.
• The proxy configuration file will not be overwritten by online updates, allowing seamless usage—unless the software is completely uninstalled and reinstalled.

• Tutorial Summary and Recommendations for Future Use
• The configuration only needs to be done once; afterwards, the software can be launched without repeating the setup or running redundant proxy tools.
• Quick and convenient, eliminating complex proxy startup steps.
• Users are encouraged to leave feedback or ask questions.

Key Terms and Definitions ⚙️

• AntiGravity: Google’s official AI integrated IDE, supporting the invocation and editing of multiple top-tier AI models.

• TUN Proxy Mode: A virtual network device mode that proxies all system traffic, adding extra load.

• Socket Proxy: A local proxy set up on a specific port (e.g., 10808) that routes traffic from selected programs only, offering more flexibility and efficiency.

• SOCKS5 Proxy: A proxy type supporting multiple protocols, suitable for handling TCP connections and commonly used in local proxy software.

• v2rayN: A widely used local proxy software for launching and managing SOCKS5 and other protocol proxies.

• washington.dll and config.json: Key configuration files in the GunProperties project that define proxy type and connection parameters.

Reasoning Flow 🧠

1. Premise: In mainland China, Google AntiGravity models require a proxy to access APIs.

2. Problem: Traditional TUN mode proxies all system traffic, increasing local network load and making usage cumbersome.

3. Solution: Use the Antigravity-proxy project to connect via a local socket proxy over LAN, avoiding global TUN proxy.

4. Operation Steps:
• Launch a local proxy tool (e.g., v2rayN) and set up a SOCKS5 proxy port.
• Download and install the AntiGravity software.
• Download the Antigravity-proxy configuration and DLL files, and copy them to the AntiGravity directory.
• Modify config.json to match the local proxy port.
• Launch AntiGravity, which automatically uses the local proxy to access models.

5. Conclusion: This method greatly simplifies the setup process, avoids resource waste, and allows seamless use of AntiGravity models.

Example Walkthrough 🎯

• Create a local SOCKS5 proxy on port 10808 using v2rayN, enabling the “Allow connections from LAN” option to ensure AntiGravity can access the proxy.

• Launch the modified AntiGravity program, select an AI model (e.g., Cloud Silence 4/5), and observe the logs showing requests successfully routed through the SOCKS proxy, confirming the proxy configuration is correct.

Common Pitfalls ⚠️

• Mistake: Using TUN mode to proxy all traffic, causing slow network and wasted resources.
• Correct: Use a LAN SOCKS proxy to route only necessary traffic.

• Mistake: Ignoring the local proxy’s “Allow connections from LAN” option, causing AntiGravity to fail to connect.
• Correct: Enable this option to ensure LAN IP access.

• Mistake: Failing to update config.json with the correct proxy port, leading to connection failure.
• Correct: Ensure the proxy port matches the local proxy software.

• Mistake: Installing AntiGravity on the C drive, which may cause permission issues.
• Correct: Install on a non-system drive.

Review Tips and Self-Test 📝

• What are the differences between TUN mode and socket proxy?

• How to configure local proxy software to support AntiGravity access?

• What changes are needed in AntiGravity’s config.json?

• Why enable “Allow connections from LAN” in the local proxy software?

1. Question: What is the main drawback of TUN proxy mode?
Answer: It proxies all system traffic, increasing local network load and making configuration complex.

2. Question: What problem does the Antigravity-proxy project solve?
Answer: It eliminates the need for TUN mode by using a local socket proxy, simplifying proxy configuration.

3. Question: What port should the socks5 proxy in config.json be set to?
Answer: It should match the port of the local SOCKS5 proxy, e.g., 10808.

4. Question: Why install AntiGravity on a drive other than C?
Answer: To avoid system permission restrictions affecting software operation and file writing.

Summary 🔍