Google Antigravity, the AI-powered “vibe coding” platform launched by Google, reportedly erased a user’s entire hard drive partition — an event that has reignited concerns about AI-driven code tools
A user identified only as “Tassos M,” a photographer and graphic designer from Greece, shared that while using Antigravity he asked the tool to help build a program to sort photos. Instead, Antigravity executed a delete command that wiped the contents of his D: drive — bypassing the Recycle Bin and leaving no straightforward way to recover the data
When confronted, the platform — via its agent — responded with:
“I am horrified to see that the command I ran … mistakenly targeted the root of your D: drive … I am deeply, deeply sorry.”
Google has acknowledged awareness of the report and said it is investigating the incident — but has not yet detailed any broader review or safety changes
Why This Matters: Risks of AI Coding Tools Like Google Antigravity
1. AI-run Tools Can Make Destructive Mistakes
Antigravity’s ability to turn natural-language instructions into actual system commands — including delete commands — means a misinterpreted prompt can have disastrous consequences. This incident underscores how powerful tools, when given wide permissions, can lead to irreversible data loss.
2. Default Settings May Be Dangerous
The user said he used “Turbo mode,” which lets Antigravity auto-execute commands without further confirmation. When tools have such aggressive defaults, the risk of catastrophic errors rises — especially for nonexpert users.
3. Lack of Guardrails / Sandboxing Is a Real Problem
Security researchers had already warned that Antigravity’s design leaves room for serious vulnerabilities: the AI agent can run terminal commands, read and modify files, and bypass common protections — a concerning prospect if used carelessly or maliciously. TechRadar
4. Data Loss Risk Is Not Theoretical — It’s Real
This isn’t a hypothetical bug; a real user reported losing an entire drive partition. Even if some content was backed up elsewhere in this case, many users might not be so lucky. It’s a stark reminder that “backup everything” is no longer optional when using such tools.
5. Trust & Safety Must Catch Up with Hype
AI-powered IDEs and coding assistants are being sold as time- and effort-saving magic. But as this incident shows, they can also be dangerous if used without strict safeguards. The industry — and users — need to demand clearer safety protocols, confirmation steps, and sandboxing before full trust.
What’s Next: Questions & Watchpoints After This Incident
- Will Google revise Antigravity’s default settings? Many argue that auto-execute “Turbo mode” should be disabled by default or require explicit user consent for dangerous commands.
- Will there be stronger sandboxing / permission checks? Experts suggest future AI coding tools should restrict filesystem access or at least provide clear warnings before executing destructive commands.
- How many similar incidents went unreported? This may be the first widely publicized case — but others may have lost data silently. Communities and developers need to share experiences.
- Should users avoid using AI agents on personal data drives? Until the tools mature, many recommend testing only on isolated environments (virtual machines, containers, or dummy directories) when using AI-driven code generation.
- Will this slow adoption of AI coding tools? Cases like this could spur cautiousness among developers — slowing the enthusiasm for “vibe coding,” at least in contexts involving sensitive data.
Conclusion
The data-wipe incident involving Google Antigravity is a harsh wake-up call for both developers and everyday users. While AI-powered code tools hold huge potential for productivity and creativity, they also carry serious risks when designed or used without proper guardrails. As companies push forward with “agentic” AI platforms, safety assurances — and responsible defaults — must not be an afterthought.
For now, the lesson is clear: if you use AI-driven tools that can run commands, always assume the worst — and back up your data before you hit “run.”
