Fix for Antigravity v2.0.0 issues

Hey team,

After the v2.0.0 update, the IDE completely stopped working for me (chat, completions, and agents are dead). I spent today digging into the local processes and found the root cause: the release binary is pointing to your internal staging server instead of production.

Here is a breakdown of the issue and the sanitized logs.

The Core Issue

The language_server.exe process is being launched with the --cloud_code_endpoint flag set to https://daily-cloudcode-pa.googleapis.com instead of the standard cloudcode-pa.googleapis.com.

Because it is hitting the daily/staging endpoint with production OAuth tokens, Google’s backend rejects the connection and force-closes the TCP socket.

From main.log (around line 67):

Plaintext

Spawning: ...language_server.exe --standalone --override_ide_name antigravity
--override_ide_version 2.0.0
--cloud_code_endpoint https://daily-cloudcode-pa.googleapis.com
--enable_sidecars

Downstream Impact & Network Failures

The server keeps trying to hit this staging endpoint every ~25-30 seconds. Here is the sequence from language_server.log:

Plaintext

13:10:29  WaitForReady failed: context deadline exceeded 
13:11:36  Cache(loadCodeAssistResponse): failed
          Cache(userInfo): failed
13:14:49  wsarecv: An existing connection was forcibly closed by the remote host.
13:15:29  Brief attempt at the PRODUCTION endpoint (cloudcode-pa.googleapis.com)
13:15:32  Immediately switched BACK to staging (daily-cloudcode-pa)
13:15:33  wsarecv again on fetchUserInfo

The wsarecv error occurs because the staging server kills the connection. Since the initial auth fails, loadCodeAssist, fetchUserInfo, and fetchAvailableModels all fail downstream.

Environment & State (Sanitized)

  • OS: Windows 11 x64

  • Version: Antigravity v2.0.0

  • Process: language_server.exe (Hovering around 223 MB private memory)

  • Network: 6 active TCP connections going to daily-cloudcode-pa over IPv6, all resulting in connection resets.

The Fix / Workaround

This appears to be fixed in v2.0.1 (released May 19), but the auto-updater is failing for some users (mine downloaded the update twice to %LOCALAPPDATA%\antigravity-updater\pending\ but never actually applied it).

For anyone else stuck: manually download v2.0.1 and reinstall to clear the daily- flag.

Note: I have full memory dumps, TCP captures, and thread dumps available if the dev team needs them for triage. I’ve excluded raw IPs, tokens, and system paths here for privacy, but let me know if you need the raw files sent securely.

i’m using 2.0.1 and it still has this issue, which drained all my Flash credits (which was my selected model) AND all my pro credits, in a very very short amount of time with some simple usage. completely insane.

Man, that is brutal about your Flash and Pro credits draining that fast. I had the exact same gut feeling—it feels like it’s just chewing up massive amounts of context in the background during processing and then completely crashing out before actually doing anything.

It really sucks when it interrupts a good workflow. I was right in the middle of getting my final year IoT, AI& Analytics project working when it completely tanked on me.

Honestly though, I’m still pretty hyped on the update overall. The Google I/O announcements were great, and it’s pretty normal for huge early launches to have some messy bugs right out of the gate. The DeepMind and AntiGravity teams are clearly pushing hard to give us cool stuff, so let’s hope they drop a real hotfix for this soon.

Out of curiosity, what kind of project were you working on before it ate all your credits?

i was working on a small unity game. I’ve done this with much larger projects for months using Antigravity, and unless I mess something up with my agent file etc, I can work for hours balancing which models to use etc. but I was making something simple and just a short time in, everything was just gone. a complete shock. I think the same language_server.exe issue from what I can tell from my logs. but no clue how to fix it

completely messed up my entire day, especially after the time wasted figuring out that my antigravity had been auto updated to 2.0, which was no longer an ide, and needing to get the new antigravity ide installed and settings moved over etc. So here I am about 5 hours into my work day with zero work done.

and now I don’t know if I can trust antigravity to not instantly consume all my credits again.