@Abhijit_Pramanik if it helps.. i literally asked Antigravity for a workaround fix b/c apparantly i cannot be the ONLY person out here dealing with this and since we cannot rollback to stable versions which i think is 1.18 I was bout to try the work around for now unless you think this will be fixed quickly. One good thing that came out of this b/c i have been burning through tokens since you guys released 1.19 altogether to try to fix this is i went and bought me a 4TB SSD ScanDisk portable drive and got rid of my old workspace which was using OneDrive.. causing all other kinds of issue so now my workspace has been reset to work off my c:/….. drive directly and i just back everything up weekly for my ENTIRE system and on a more regular basis as far as Antigravity is concerned b/c of all my .secrets files etc that hold priceless information so I guess this experience has at least help me have my environment and projects set up like most developers would.. anyways this is what Antigravity just spit out for the workaround if it helps:
I have successfully diagnosed the local Agent Manager logs and found the exact issue causing the infinite spinning scenario. You are absolutely correct that this is an IDE/Agent Manager bug related to how it handles the chat history for root drive paths.
Diagnostic Findings
The explicit error happening repeatedly under the hood in C:\Users\jimmy\AppData\Roaming\Antigravity\logs\… \window5\exthost\google.antigravity\Antigravity.log is:
log
[info] E0226 15:42:46.467264 39108 interceptor.go:74] /exa.language_server_pb.LanguageServerService/StreamAgentStateUpdates (unknown): update is too large
[info] I0226 15:42:57.767257 39108 client.go:56] CEL: Sending error - type=LS_ERROR ideName=antigravity appName=antigravity_desktop version=1.19.5
[info] E0226 15:42:42.925305 39108 interceptor.go:74] /exa.language_server_pb.LanguageServerService/RefreshMcpServers (unknown): loading already in progress
The Root Cause
When the Agent Manager attempts to retrieve a chat that has your root drive (C:\) set as the workspace, it aggressively gathers filesystem context for the state update. This bloats the internal chat history file to a massive size.
Checking C:\Users\jimmy\.gemini\antigravity\conversations, I see that the specific chat file for our “Antigravity Master Migration” (36484c86-2333-4173-9ee3-1ed29f23a9fe.pb) has ballooned to 12.5 MB due to the root drive context payload!
When the IDE tries to load this chat, the Agent Manager attempts to send the entire state over its internal gRPC stream (StreamAgentStateUpdates). Because it is ~12.5 MB, it exceeds the strict gRPC maximum message limit (which typically defaults to 4MB). The backend gRPC channel drops the payload with the exception update is too large, and the frontend is left eternally waiting for a state update (loading already in progress), resulting in the “infinite spin.”
The Workaround (To Recover Safely)
Since we simply can’t force the current Agent Manager (v1.19.5) to stream a 12.5MB state object over gRPC yet, we have to forcibly untether the application from booting into this broken chat—without actually throwing the chat away permanently.
Here is the exact workaround to securely recover your IDE environment:
-
Close all instances of the IDE.
-
Navigate to your local conversations directory: C:\Users\jimmy\.gemini\antigravity\conversations
-
Move the problem file(s): Locate the file 36484c86-2333-4173-9ee3-1ed29f23a9fe.pb (and any other unrecoverable chats if applicable). Do not delete it! Just cut and paste it somewhere safe, like a C:\Antigravity-Master\Chat_Backups folder.
-
Relaunch the IDE. Because the IDE’s last active chat is suddenly “missing,” it will gracefully fall back to creating a fresh, empty chat (or loading a stable older one) without triggering the update is too large limit. The infinite spin will vanish.
Moving forward: Your chat is safely preserved as a .pb file. Once the Agent Manager pushes a patch to expand the gRPC MaxCallRecvMsgSize or optimize root directory polling, you can easily drop that .pb file back into the conversations folder and the chat history will be fully recovered!