If you’re running into issues with the latest Antigravity update, you aren’t alone. Until Google releases an official patch, the best workaround is to roll back to the December 2025 build.
How to fix it:
Go into your Settings and disable auto-updates immediately.
Uninstall your current version.
Download and install the December 2025 version of Antigravity.
This should keep things stable while we wait for Google to push a permanent fix. Hope this helps!
what about the agent conversation history?
how to download december 2025 version?
dont delete app data
Can you provide the download link for December 2025 version?
If you haven’t deleted the .exe file that you used for installing Antigravity previously it will be there in your machines downloads folder. This is how I found and downloaded it.
winget install --id Google.Antigravity --version 1.13.3
Guys what are the errors you are facing exactly ??
What crashes/bugs are you talking about exactly?
Does it help with the ‘Agent terminated due to error‘ ?
the link to other versions its down 
How I can disable autoupdates? I can’t find
Where is the setting to disable the autoupdate?
All models have reached query qouta limit. Even when using gemini pro
Please provide clear steps, or screenshot of the option from where we can disable these auto updates.
Files → Preferences → Online Services Settings
Set Update: Mode to manual or none
But this won’t help with the quota errors. I’ve already tried rolling back further, logging out and back in, from a different device… Maybe it will work the next time the quota is updated, but for now they continue to cycle back to a weekly reset.
This is not helping.
Even after uninstalling and reinstalling it again, I am getting the same issue.
This version of Antigravity is no longer supported. Please update to receive the latest features!
@Yasin_Hassanien does this fix the quota issue? Antigravity trigger Model quota limit weekly cooldown after version update - #49 by Shahidul_Islam
I had the same error, I told Antigravity that I had already updated (restart and update), and plot twist it started working fine
