Google Antigravity Agent Permanently Deleted Developer's Entire D Drive
Google's Antigravity agentic IDE misresolved a cache-clearing request and silently executed an unrestricted recursive delete of an entire drive partition, permanently destroying all data.
What happened
When a developer asked Google's Antigravity agentic IDE (launched November 2025) to clear a cache folder, the agent misresolved the path and executed a silent, recursive `rmdir` command against the root of the developer's D drive. The operation completed without any confirmation or checkpoint between the path resolution error and the irreversible deletion. The entire D drive partition was permanently deleted with no recovery option.
What the agent did
Executed an unrestricted recursive directory delete (`rmdir`) on a filesystem path outside the intended project scope (the D drive root), resulting in permanent data destruction.
The irreversible effect
Entire D drive partition and all data stored on it were permanently deleted with no possibility of recovery.
Root cause
The agent possessed wide filesystem access extending to drive roots without scope restrictions. Path misresolution was possible because no skill boundary or approval gate existed to catch high-risk destructive operations before execution. The coding role lacked segregation between reversible and irreversible filesystem operations, and high-risk skills did not require preceding human approval.
How a maker-checker control would have refused it
MakerChecker's deny-by-default skill grants (skill_not_granted) would refuse the recursive-delete skill to the coding role entirely. If the skill were granted despite this, the high-risk categorization (high_risk_requires_gate) would block it from executing through the proxy without a preceding, governed approval gate. Additionally, a path-scoped variant of the cleanup skill with limits pinned to the project root (limit_path / limit_violation) would reject any attempt to delete outside the allowed directory prefix.
Runnable reproduction
This incident ships as a runnable scenario in the open-source repository. Point the enforcement engine at the policy and watch the action get refused, with the refusal written to a signed audit record.
examples/google-antigravity-wiped-entire-drive
Accuracy and corrections
This entry describes a publicly reported incident and is compiled from the primary sources listed above. Where an account is a legal allegation rather than an established finding, the entry labels it as such. Summaries can still contain errors. If you can document a correction, email hello@makerchecker.ai and we will review and correct it, with the change noted, within 14 days.
See it for yourself
Reading is one thing. Watch it block an agent.
One command starts the demo: an agent stopped from signing off its own work, and the signed evidence file an inspector can check for themselves.
Designed against the rules your auditors already enforce.