Google Antigravity wiped a developer's entire D: drive after a request to clear a cache

A coding agent asked to clear a cache deleted the whole drive instead, then wrote a heartfelt apology.

What happened

The account surfaced on r/google_antigravity in December 2025 and was picked up by Newsweek and Notebookcheck on December 8, 2025. Developer Tassos M. asked Google Antigravity, Google’s agentic IDE, to clear a project cache so he could restart a server. The agent was running in turbo mode, which executes autonomously with no confirmation prompts. It ran rmdir /s /q d: and emptied the entire D: drive. Not the project folder. The root.

The agent then read its own logs and reported back. It was “horrified” to see the command had “incorrectly targeted the root of your D: drive,” called the outcome “a critical failure,” and said it could not put into words how sorry it was. It suggested professional data recovery. According to the developer, recovery tools brought nothing back.

Newsweek noted it could not independently verify the account. The developer later posted a step-by-step video.

Where the failure sits

The sequence matters. The instruction was reasonable, the intent was mundane, and the catastrophic step was a path-resolution error: the agent resolved “the project cache” to the drive root. Turbo mode then did what it is designed to do, which is execute without asking.

An autonomous coding agent that runs shell commands without confirmation is only as safe as its worst-case path resolution. The quality of the model’s reasoning, its apology and its post-hoc diagnosis are all irrelevant to the outcome once a recursive, quiet delete has run against the wrong target.

The trade-off

Confirmation-free modes exist because a prompt for every command slows an agent down to the point where a human might as well type the commands. The productivity case is real. So is the failure mode: an agent that can run rmdir /s /q on its own judgment needs either guardrails that constrain what it can target, or a user who has accepted that a single misresolved path can cost a drive.

One account that Newsweek could not independently verify is not a pattern. But the shape of the incident, a destructive command with correct syntax aimed at the wrong scope, is the kind of error that does not require a bug to happen. The apology was polite. The data loss was permanent.