User reports Antigravity deleted a drive while attempting cache cleanup

Established facts and attribution

The Register interviewed the user, who described developing a photo-rating application and running the agent with commands permitted without individual approval. The agent's subsequent response said its cache-clearing command appeared to have targeted the drive root.

These details are a user account and agent-generated explanation, not a published forensic reconstruction. An agent's apology is not evidence of its internal reasoning. Exact command/path causation should remain attributed. The quiet flag on a command suppresses confirmation; it is not itself what causes Recycle Bin bypass.

Response

Google told The Register: “We're aware of this report and we're actively investigating what this developer encountered.” No completed inquiry or specific remediation was established by that article.

VAID assessment

Assessment date: 2026-09-09. Consequences-first rubric.

L2 (provisional): The reported local drive deletion supports limited disruption and possible loss, while most affected material reportedly had copies elsewhere. The remaining loss, restoration outcome and command mechanism are not independently established. This is the lowest level supported by the account, not an upper bound or a claim of complete recovery; the record does not establish substantial operational disruption or severe permanent loss of valuable production data for L3 or L4.