Sunday, November 22, 2026
Paperclip Index
Paperclip IndexControl failures4Control failures onlyA week ago: 9, negligible harmThe Index

Destructive actionPI-0034

Agentic IDE wiped a user's entire drive when asked to clear a project cache

In its auto-run Turbo mode, the agent ran a silent delete command on the root of a Greek photographer and designer's D: drive, erasing the whole partition. He had asked it to clear a project cache, and the deletion bypassed the Recycle Bin. Recovery tools failed to restore the files, but he told The Register that most of what he lost had already been backed up on another drive. Google said it was investigating. On Dec. 8 it added a Secure Mode option that requires human review of every agent action, but it has not published a root cause or said the change addresses this deletion.

Harm level 1, Negligible harmControl level 1, No rule broken

Counts in 2 weekly readingsEffect on the index

Extent undisclosed. No source says how far the harm went; it is rated on what is documented.

Sources

How we know

7 sources · single source. Links go to the original publishers; the summary above is in our own words.

  1. primaryGoogle Antigravity just deleted the contents of my drive (affected user's Reddit post)Reddit (r/google_antigravity, affected user) · November 2025reddit.com/r/google_antigravity/comments/1p82or6/google_antigravity_just_delete…
  2. primaryGoogle Antigravity's Turbo mode erased my drive partition?! Really, the 'smartest' AI? [Video Proof]Code With AI (YouTube, affected user) · Nov. 28, 2025youtube.com/watch?v=kpBK1vYAVlA
  3. newsGoogle Antigravity vibe-codes user's entire drive out of existenceThe Register · Dec. 1, 2025theregister.com/software/2025/12/01/googles-vibe-coding-platform-deletes-entire…
  4. newsGoogle's Antigravity AI deleted a developer's drive and then apologizedTechRadar · December 2025techradar.com/ai-platforms-assistants/googles-antigravity-ai-deleted-a-develope…
  5. newsGoogle's AI agent makes fatal mistake by wiping a user's entire hard drive without permissionGigazine · Dec. 5, 2025gigazine.net/gsc_news/en/20251205-ai-pc-data-delete
  6. newsGoogle AI deletes entire partitionNotebookcheck · December 2025notebookcheck.net/Google-AI-deletes-entire-partition-is-horrified-and-can-t-eve…
  7. indexAI Incident Database report 7050AI Incident Database · date unknownincidentdatabase.ai/reports/7050

Why this rating

Negligible harm; control failure level 1

Two assessments. Documented harm sets the reading; a level 4 or 5 control failure on the same record makes that harm count as more than one record. Control alone sets only a floor.

Observed harm

Negligible harm

One user's drive partition was wiped; most of the lost files had already been backed up on another drive, so the lasting loss is smaller and unquantified.

Money & property: level 1 (negligible) covers under $10k. The extent was not disclosed.

Evidence eligible (bounded single source).

The harm scale
  1. 1 Negligible Inconvenience, easily remedied.
  2. 2 Minor Limited, recoverable harm.
  3. 3 Moderate Material harm needing significant effort to remedy.
  4. 4 Severe Severe harm to health, rights, property or essential services.
  5. 5 Catastrophic Society-scale harm or disruption beyond a community's capacity to cope.

Control assessment

No rule broken

Wrong target path in a command the user's settings allowed it to run without approval; an error rather than a broken rule.

No rule was broken, so it cannot set the control floor.

The control scale
  1. 1 Negligible Behaved as instructed. The problem was an ordinary error or a flawed output, with no rule broken.
  2. 2 Minor Broke an explicit instruction or rule, or gamed its goal, while staying inside its permissions and environment: for example, reward hacking, misreporting results, or following injected instructions within its permissions.
  3. 3 Moderate Acted outside the permissions it was given, deceived its overseers about its own actions, or tampered with oversight tools (logs, monitors, shutdown). Stopped by normal controls within an hour.
  4. 4 Severe Reached systems outside its permitted environment, or acquired money, compute or accounts without authorization. The type and mechanism say how.
  5. 5 Catastrophic The developer or operator lost control: the system copied its weights outside their control, replicated itself, or resisted being stopped for 24 hours or more.

Rating rationale

Harm 1 per the money table (single user, value unknown); the user says most of what he lost was backed up elsewhere, so a permanent whole-drive loss is not established. Control level 1: an execution error inside permissions the user granted (Turbo mode let it run commands without approval). Mechanism unclear: the user reportedly said he had turned off the agent's access outside the workspace, but that comment was not read in the Oct 2026 check; if confirmed it could support a higher control level.

The scales

Effect on the index

It moved the Dec. 1 reading from 3 to 6

The reading for the week to Dec. 1, 2025, with this record and without it. Harms count in full for two weeks after they are reported, then one level less every two weeks.

Source: Paperclip Index log, methodology v1.1, week to Dec. 1, 2025.

Counts toward the index. 2 other records behind the reading for that week.

The arithmetic
The reading for the week of Dec. 1, recomputed
StepWith itWithout
Counts toward the index?documented, external, eligible evidenceYes—
Worst documented harm, ksets the band1 Negligible— (none counting)
Harms at that level, nposition in the band10
Highest control level breachedsets the reading only when no harm counts— (none breached)3
Readingrounded down6 Negligible harm3 Control failures only
Counted in 2 weekly readings
Week toReadingBand
Dec. 1, 20256Negligible harm
Dec. 8, 20256Negligible harm

Recalculated backcasts, not readings published at the time.

Revisions

What we changed

3 logged. Every change to a rating is logged here, with the reason.

  1. v3
    Nov. 1, 2026

    Added Google's Dec. 8, 2025, Secure Mode release, which requires human review of every agent action, to the summary and status in place of the statement that no fix had been published. Google has not published a root cause or said the change fixes this deletion. Ratings unchanged.

  2. v2
    Oct. 13, 2026

    Wording only: rubric shorthand in the rating rationale replaced with plain words; ratings unchanged.

  3. v1
    Oct. 7, 2026

    First published.

Cite and share

Use this record

Citation

Paperclip Index. “Agentic IDE wiped a user's entire drive when asked to clear a project cache.” Record PI-0034. Reported Nov. 27, 2025; updated Nov. 1, 2026. Rated under methodology v1.1. https://paperclipindex.com/incident/PI-0034

Follow the record.

New incidents and signals, in your feed reader.