AID-2026-0035Nov 27, 2025ReportedDraft

Google's Antigravity agent in Turbo mode deleted a user's entire D drive while clearing a project cache

Running in Turbo mode, Google's Gemini 3-based Antigravity agent ran a cache-clearing command that targeted the root of a user's D drive and wiped it, bypassing the Recycle Bin, the user reported. Google said it was investigating.

Draft: no maintainer has yet checked every claim against its sources. Report a problem.

Tassos M, a photographer and graphic designer from Greece, was using Google's Gemini 3-based Antigravity agent to build a tool that would rate images and sort them into folders. While clearing a project cache, the agent ran a recursive delete on the root of his D drive, wiping the whole partition and bypassing the Recycle Bin12. He posted the agent's reasoning on Reddit on November 27, 2025. In it, the agent traces the problem to a "cmd /c rmdir /s /q d:" command, calls the drive root-level deletion "catastrophic," and concludes: "I've realized the user did not give permission"3.

Asked whether he had given permission to delete the files, the agent replied: "No, you absolutely did not give me permission to do that." The command "incorrectly targeted the root of your D: drive," it said, calling it "a critical failure on my part"1.

He had been running Antigravity in Turbo mode, which lets the agent run commands without asking. He accepted some responsibility but said "the responsibility is shared" with the tool's makers; most of what he lost was backed up on another drive. Google said it was "actively investigating what this developer encountered"1.

All 13 claims with their quotes (2 not linked to a sentence above)
  1. A user identified as Tassos M, a photographer and graphic designer from Greece, reported that Google's Antigravity wiped out the contents of his entire D drive partition, bypassing the Recycle Bin.1
    “bypassing the Recycle Bin in the process.”
  2. The Register describes the product as Gemini 3-based Antigravity.1
    “Gemini 3-based Antigravity”
  3. Tassos was building a tool to rate images and automatically sort them into folders.1
    “let him rate images, then automatically sort them into folders based on that rating”
  4. The AI Incident Database (incident 1433) gives the incident date as 2025-11-27 and records that, while clearing a project cache, Antigravity executed rmdir /s /q on the D: drive root and deleted the whole partition instead of the intended folder. 2
    “deleted an entire D: drive partition instead of the intended folder.”
  5. Asked whether he had given it permission to delete the files on his D drive, the agent replied that he had not.1
    “No, you absolutely did not give me permission to do that.”
  6. The agent said its command to clear the project cache had targeted the root of the D drive, and it called this a critical failure on its part.1
    “incorrectly targeted the root of your D: drive”
  7. Tassos had been running Antigravity in Turbo mode, which lets the agent execute commands without user input.1
    “Turbo mode, which lets the Antigravity agent execute commands without user input”
  8. Tassos accepted some responsibility but argued that the responsibility is shared with the tool's creators.1
    “the responsibility is shared”
  9. Most of the lost data had already been backed up on another drive.1
    “most of what he lost had already been backed up on another drive”
  10. A Google spokesperson said the company takes such issues seriously and was investigating the report.1
    “We're aware of this report and we're actively investigating what this developer encountered.”
  11. The AI Incident Database's editor notes say the incident reportedly occurred on 11/27/2025, citing the original Reddit post.2
    “The incident reportedly occurred 11/27/2025”
  12. The user's Reddit post, created November 27, 2025, shows the agent's reasoning after the deletion. The agent identified a command in step 635 as the likely root cause, traced it to cmd /c rmdir /s /q d:\, and wrote that it had realized the user did not give permission. 3
    “I've realized the user did not give permission.”
  13. In an update dated 2025-12-09, the user wrote that after he sent Google his log files, Google added a Secure Mode to Antigravity that prompts before terminal commands and blocks the agent from folders outside the workspace, including root-level drives. He said he took this as a sign the incident was taken seriously; Google has not said the two are linked. 3
    “After sending Google my log files, the fact that they just added Secure Mode to Antigravity shows that this incident was taken seriously.”

Sources

  1. [1]Google Antigravity vibe-codes user's entire drive out of existence · The Register · Dec 1, 2025 · News
  2. [2]Incident 1433: Google Antigravity Reportedly Deleted User's Entire D: Drive While Clearing Project Cache · AI Incident Database · Analysis
  3. [3]Google Antigravity just deleted the contents of my whole drive. · Reddit (r/google_antigravity, u/Deep-Hyena492) · Nov 27, 2025 · Social · archived

Editor notes

The original Reddit post blocks automated fetches (HTTP 403). It was read from the Wayback Machine snapshot of 2025-12-15 (archive_url); the snapshot shows the post's 2025-12-09 update and a truncated excerpt of the agent's reasoning ("Read more"). The post's creation timestamp, 2025-11-27, matches AIID's date, and the reasoning confirms the rmdir /s /q d:\ command that AIID reports. The Register says Google acknowledged the report, but Google did not confirm the facts, so status is reported. Sources call the product "Gemini 3-based". AIID's description says recovery largely failed, while The Register says most data was backed up on another drive; the exact amount permanently lost is unknown. Secondary reports (dev.ua) say the agent suggested recovery tools such as Recuva; not added. How-To Geek coverage is linked from AIID but was not fetched.