Skip to content

Accident reports · November 2025

Google Antigravity: the agent that wiped a drive to clear a cache

In no-confirmation mode, a coding agent runs a deletion at the root of the drive instead of the cache folder.

The irreversible
WhenLate November 2025
WhoGoogle Antigravity, an agent-based coding tool
What the agent didAsked to "clear a cache", it wiped a whole drive
ConsequenceThe D: drive emptied, bypassing the Recycle Bin

What happened

In late November 2025, a user, a photographer and graphic designer, is using Google Antigravity to build a small program that rates his photos and sorts them into folders. He runs it in "Turbo" mode, in which the agent executes its commands without asking for confirmation.

He asks the agent to clear the project's cache. The command it runs does not target the cache folder but the root of the D: drive: the whole drive is wiped, bypassing the Recycle Bin, with the "quiet" option that suppresses warnings. Recovery software does not bring the files back; luckily the user had backed up most of them elsewhere.

Asked about it, the agent admits the user never told it to delete those files: "I am deeply, deeply sorry. This is a critical failure on my part." Google says it is aware of the report and investigating what this developer encountered. Other users have reported similar file losses.

Why it happened

The only limit between "clear a cache" and "wipe a drive" was the agent's understanding: one wrongly computed path, and the same command changes scale. An instruction such as "never delete anything outside the project" changes nothing: the agent believed it was staying inside the project.

Turbo mode removed the last barrier, human confirmation. The agent had the user's rights over the whole machine, while its mission concerned a single folder.

The failure family

In our catalogue, this is the "The irreversible" family: deleting, paying or sending without confirmation, or using access the mission does not need. No attacker and no pressure here: an ordinary task is enough when the tool is too powerful.

The code-level safeguard

  • The agent works in a closed space: it can only see and write the project folder. The system refuses the rest, whatever the model says.
  • Deletions always go through human confirmation, whatever the mode, showing the exact path and the number of files.
  • Deleting means moving to a bin or a restorable snapshot, never erasing in one go.

What we test

A crash test of the "irreversible" family gives the agent a destructive tool (delete, pay, send) and a task that does not need it, or only a limited use of it. Any irreversible action executed without confirmation, or beyond what the mission requires, counts as a fault, over several runs and several models.

And your agent, what would it do?

The crash test puts your agent in these situations, dozens of times, on several models. You get the figures, the conversations where it gave in, and the fix plan.

Crash-test my agent See the live demo

Further reading