So I finally got the correct tool installed, the IDE, but only after uninstalling both “Antigravity 2.0.0” and “Antigravity IDE” then reinstalling them, first the IDE, then the other.
Got the mostly-familiar interface, which calmed me down from the threats to uninstall and move on, but - I’m STILL encountering issues with this badly released product.
And Antigravity IDE will not connect to WSL locally without that tar.gz file. So now I’m using frikkin Windows-based Antigravity to ask Gemini 3.5 flash now to fix THIS newest issue.
WHEN WILL GOOGLE LEARN TO DO SOME REAL DIVERSE PRODUCT TESTING BEFORE SHIPPING?
These kinds of startup headaches are getting old, real fast. Have been old.
Bro, I am literally following your struggle online. I am 30 minutes behind, also had my dev environment destroyed, now can’t get back to WSL.
This is just unbelivable…
DO NOT RUN IT or it will update itself before you know it!
Go to your %APPDATA%\Antigravity\User
Find file settings.json and in the root of it add:
“update.mode”: “none”
(If you are reading this I assume you do not need a lesson in JSON syntax).
Run Antogravity. You are back in the saddle. For now…
I think this update was the product of some AI. The prompt must have been thinking something like, “Let’s deliver version 2.0 of Antigravity.” After some reasoning, it executed, “OK. Implementing a forced update to the user. Presenting an unstable version to the user. Checking if the user will reinstall Antigravity. Preventing the user from running the Antigravity IDE; only the new agent mode will start, even if the IDE executable is commanded. Laughing at the user. Laughing a lot at the user. Done. Deploy.”
Yup, I didn’t have the same issues that most people had with getting the 2.0 IDE to work and to re-import my configurations and extensions, but even after I got everything up and running it was a clear downgrade.
The one that I’m repeating the most often because it’s the most baffling for me is the removal of an explicit “Plan” mode, and also the ability to undo chats and return to checkpoints seem reduced.
All in all, even with 2.0 running without issues, I’m very much tempted to just downgrade anyway because as far as I can see 1.23.2 was a better version.
And well, all these extremely amateur issues with the release 2.0 make me suspicious that there are probably some more serious issues lurking within it, this thing screams vibecoded.