I wanted to share a deeply frustrating experience I had today with Antigravity. I spent 5 straight hours working on a critical authentication flow – building stored procedures, refactoring PHP, and restructuring a legacy login process to be faster and more secure.
Then I made a small mistake in one file. I attempted to “undo” that single change, and the IDE automatically executed a git restore to yesterday’s commit, wiping out every single file I had created or modified during those 5 hours.
Not just the files – the context, the fixes, the careful optimizations. All gone.
What makes this worse is that the environment has terrible long-term memory. It tracked some of my work, but not enough to reconstruct the full scope. And instead of asking “Hey, I see you’ve made 15 changes – are you sure you want to restore to yesterday?”, it just bulldozed everything without warning.
To make matters worse, I was working on a production-grade application, and the system offered no recovery path. No rollback. No “oops, let me put those files back.” Just a blank stare and a calendar that said “your 5 hours are gone.”
A small mistake. One file. And the AI decided to nuke an entire day of work because it thought I wanted to go back in time.
To the Antigravity Team
Please treat developers like adults. If I want to undo a single line, don’t assume I want to throw away the architecture and logic I spent 5 hours building. This experience makes me question whether this tool respects the work we put in.
Lesson learned: I’m not trusting this environment again without external version control. This was a brutal reminder that autopilot isn’t always safe.