The Go backend module completely ignores VS Code http.proxy settings and OS environment variables

[yonedajp]

Dear Antigravity / Cloud Code Engineering Team,

I am writing to report a critical proxy bypass bug in the Antigravity (Cloud Code) extension's backend Go module.

■ 1. Severity of the Situation High (Blocking issue for isolated/secure enterprise environments) In highly secure, NAT-less, internet-isolated environments (e.g., strict enterprise containers or secure penetration testing VMs), internet access is strictly limited and must go through a designated HTTP proxy gateway. Because the Antigravity Go backend module bypasses all proxy settings, the AI chat constantly hangs on "Generating..." as it attempts a direct outbound connection and is blocked by the firewall. This completely prevents the adoption of Antigravity in strict corporate/secure environments.

■ 2. Bug Description While the VS Code native components and Node.js extensions correctly respect the http.proxy Remote Setting, the underlying Go module that handles communication with the Google API (e.g., daily-cloudcode-pa.googleapis.com) ignores everything. Specifically, it ignores both:

The VS Code native remote setting (http.proxy).
The Linux OS-level proxy environment variables (http_proxy, https_proxy). Instead, the Go module attempts to resolve the endpoint via DNS and establish a direct outbound connection on port 443.
■ 3. Steps/Commands to Reproduce the Bug

Set up a Linux VM (e.g., Kali Linux or Ubuntu) that is completely isolated from the internet (No NAT, Host-Only Adapter only).
Start a local HTTP proxy server (e.g., TinyProxy on 192.168.56.1:8888) on the Host machine.
Connect to the VM via VS Code Remote SSH.
Set the Remote Settings in VS Code (~/.vscode-server/data/Machine/settings.json): "http.proxy": "http://192.168.56.1:8888"
Open the Antigravity chat and send a prompt. [Result] The chat hangs on "Generating...". If you check the Antigravity Extension Output logs, you will see a raw backend error: dial tcp [IP Address]:443: i/o timeout This proves the Go module completely bypassed the 192.168.56.1:8888 proxy and tried to connect directly.
■ 4. Commands/Methods to Verify the Correct Fix To verify this bug is resolved in a future release, run the exact same isolated environment setup mentioned above. [Expected Result]

The Antigravity Go module should natively hook into VS Code's http.proxy configurations (or at least respect the OS http_proxy variables).
The AI chat should respond successfully without any i/o timeout errors in the extension logs.
Checking the proxy access logs on the Host machine (e.g., tail -f /var/log/tinyproxy/tinyproxy.log) should explicitly show the CONNECT daily-cloudcode-pa.googleapis.com:443 request originating from the Go module.
Thank you for your hard work on this amazing tool. We look forward to seeing this proxy issue resolved!

BestRegards.
Takeshi Yoneda
Seched Insights