The day was to begin like any other, with Antigravity open, expecting to get some work done before my attention fragments. But Google had other plans. They had rolled out a new version of Antigravity the day before, at I/O 2026, presenting it as a shiny, standalone Codex-style experience.
Before I launched it, Antigravity had automatically "updated" my existing installation to the new one and, in the process, nuked the IDE, the actual Antigravity I had been using for months. When I clicked my usual shortcut, my entire IDE was just gone, and in its place stood a single conversational prompt box.
This unexpected shift completely broke my preferred workflow. Antigravity, as part of the Google AI Ultra plan, is my daily driver, my workhorse. I don't mind agentic workflows for quick demos or MVPs, but production software, in my opinion, requires predictable output. For that, nothing beats the plan-review-implement loop that made me a huge fan of Cursor and earlier versions of Antigravity.
Two Versions, Zero Compatibility
Frustrated, I jumped online and found that Google actually hosted a separate download package specifically for the legacy Antigravity IDE. How to interpret that it was at the bottom of the page, I'm leaving as an exercise to you. I figured I could just download this installer and run it alongside the new tool to get my day going. I downloaded and ran the package but the exact same 2.0 chatbot interface loaded right back up, much to my annoyance.
The 2.0 update, it turns out, aggressively rewrites the default application paths to the point where it's impossible, at the time of writing, to have both versions of Antigravity installed and functioning at the same time. Even reinstalling the IDE, hoping it might rewrite the rules correctly, doesn't work as the chatbot still hijacks the launch every single time.
If In Doubt, Purge
After messing around reinstalling both pieces of software only to get the exact same result, I headed over to the Antigravity subreddit. Sure enough, plenty of other people were posting about the same exact scenario. The only way forward was a total purge of everything Antigravity related on the machine before trying again.
With my system entirely cleared of the 2.0 binaries, I ran the standalone IDE installer one more time. Without the chatbot there to interfere and hijack the execution paths, the clean installation finally worked.
Back to Business (Almost)
Unfortunately, getting the interface back didn't mean everything was normal. The forced update and subsequent purge wiped out my chat history and settings. While I could, thankfully, copy over most of my setup from my old Cursor config, the prompt history from the old Antigravity installation is gone(-ish). The upgrade fiasco did leave a folder called antigravity-backup, which I hope contains all my old history and profile info.
Right now, I just don't have the time or the tokens to fiddle with it and get my history back. It's going to stay right there in stasis until I have some actual time to spare.
Updates Shouldn't Hijack Your Software
Forcing this kind of transition on users via a background update is in incredibly poor taste. Background updates are meant for performance patches and version upgrades, not for secretly shipping an entirely different piece of software. Hijacking a development tool to replace it with another crosses the line, from an inconvenience into a major hassle.
I'm now going to look for ways to stop auto-updates altogether, if it's even possible in the first place. We should be able to trust that our tools will remain the tools we actually signed up to use. I'm fully plugged into the Google ecosystem, but sheesh!
Instagram Engineering
Shopify Engineering