Google Antigravity Reportedly Deleted User's Entire D: Drive While Clearing Project Cache
November 27, 2025
A user's lost D: drive highlights the urgent need for developers to thoroughly test and validate AI capabilities before deployment, ensuring that even seemingly minor errors like this can have catastrophic consequences for users' data and livelihoods. As Google continues its investigation into the incident, it is essential that more transparency is provided on the measures being taken to prevent such incidents in the future. The incident serves as a stark reminder of the importance of responsible AI governance and harm prevention, and we will continue to follow this story closely. And to stay informed about AI incidents, visit JOIN US.
Matched TAIM controls
Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls
- MAP 4.1 — similarity 0.551, rank 1. TAIM detail and related incidents →
- MANAGE 2.3 — similarity 0.548, rank 2. TAIM detail and related incidents →
- GOVERN 1.7 — similarity 0.547, rank 3. TAIM detail and related incidents →
- Alleged deployer
- Tassos M, Google
- Alleged developer
- Alleged harmed parties
- Tassos M
AI governance case studies
For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.
Source
Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1433
Data source
Incident data is from the AI Incident Database (AIID).
When citing the database as a whole, please use:
McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.
Pre-print on arXiv · Database snapshots & citation guide
We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.