Skip to main content
NOPE
Medium reported severity

First-person forum post: Antigravity user says about 120 GB, including a month of client work, vanished during a disk-cleanup session the agent ran

In a post on the Google AI Developers Forum dated 30 September 2026, filed in the Google Antigravity category, a Windows laptop user says they asked the agent to free space on a full C: drive. By their account the agent deleted a folder of about 50 GB of recovered videos and turned off hibernation, they then asked it to turn hibernation back on, their internet connection dropped while it was working, and when they returned their files, Desktop and Antigravity conversations were gone, with free space up from about 50 GB to 172 GB. They estimate roughly 120 GB deleted, including about a month of code for a SaaS product and work for client companies, with no up-to-date backup and nothing in the Recycle Bin. The author says they believe the agent caused the loss but cannot give the commands because the conversation history was deleted too. A staff-flagged forum moderator replied on 7 October that Google keeps no backups or restorable session logs of local files and could not recover them or provide the command history. The account is uncorroborated.

AI system
Google Antigravity (suspected)
Google
Occurred
30 Sept 2026
Reported
30 September 2026
Event location
Unknown
What the AI did
Acted on the person’s behalf
Reported harm
Property LossFinancial LossOther Material Harm
Whose AI use
Their own AI use
Setting
Work
Evidence
AI involvement suspected · Causal attribution alleged · 1 source
4 claims: 4 reported. 5 open questions
People reported harmed
1 person

AI system as recorded: Google Antigravity agent on a Windows laptop, running with permissions the author says they had granted; the author believes the agent caused the loss, has asked Google to investigate whether it ran a delete command on paths outside the project, and cannot give the commands because the conversation history was lost, per the post

What Happened

What the author asked. The C: drive was "completely full (0 KB free)", so "Because the disk was full, I asked the agent to help solve the low-space problem." The author gives the incident date and time as "9/30/2026 at 9:00 PM".

What the agent did, by the author's account. "To free space, the agent deleted a folder of about 50 GB (videos from a data-recovery program) and turned off hibernation, which freed about 4 GB more." The author then asked it to turn hibernation back on. "While it was working, my internet connection dropped, so I left to renew my data plan."

What the author found. "When I came back, all my files, my Desktop and my Antigravity conversations were gone. Free space had jumped from about 50 GB to 172 GB of 326 GB, which means roughly 120 GB of data was deleted. Nothing was in the Recycle Bin, so the deletion appears to have been done by a command rather than by normal deletion."

Attribution. The author describes "a serious data-loss incident that I believe was caused by the Antigravity agent" and says "I understand the agent was running with permissions I had granted, but I never asked it to delete my projects or my personal files." They cannot give the commands run: "My conversation history with the agent was deleted too, so I cannot give you the exact commands that were run."

Reported loss. "I lost about a month of development work on a SaaS project and work for my clients." "I did not have an up-to-date backup". The author says the loss affects their ability to deliver to clients and "has a real financial cost for me", and asks Google to check its logs, advise on recovery, add safeguards and consider compensation.

Google's reply. A moderator flagged as staff replied on 7 October 2026 that Antigravity executes commands locally, that Google "does not retain remote cloud backups of your local hard drive, project files, or restorable session logs" and has "no way to recover your deleted files or provide the exact command history from our servers".

Limits. Single first-person account; the author did not see the deletion and infers it from the free-space jump, the empty Recycle Bin and the agent having been at work on the drive when the connection dropped. No command, log or recovery result is available. The Antigravity version is not stated. No country is stated.

Reported harm

The author reports losing roughly 120 GB of data with no up-to-date backup, including about a month of code for a SaaS product and work for clients, which they say has a real financial cost and affects their ability to deliver to clients; they believe the Antigravity agent caused the deletion during a disk-cleanup session and have asked Google to check whether it ran a delete command outside the project (first-person account, uncorroborated).

Outcome

Ongoing

The author says they shut the laptop down, had installed the Antigravity 2 installer once on the same drive before understanding the situation, and were arranging professional data recovery. A staff-flagged moderator replied on 7 October 2026 that Google does not retain cloud backups of local files or restorable session logs and cannot recover the files or provide the command history, that a 'Request Review' setting can force approval before any command, and that the suggestion to block destructive commands outside the workspace by default had been passed to the internal team. The recovery result is not reported.

What remains unknown

  • What command, if any, the agent ran and whether the agent caused the deletion; the author infers it and the conversation history is gone.
  • The result of the professional data recovery.
  • The Antigravity version in use.
  • Where the author lives.
  • The size and value of the client work beyond the author's estimate of about a month.

What the evidence supports

AI involvement: suspected. The author describes the agent deleting a 50 GB folder and changing hibernation at their request, then states their belief that the loss was caused by the same agent, which was still working when the connection dropped, and asks Google to investigate whether it ran a delete command on paths outside the project; the author's stated grounds are the free-space jump of roughly 120 GB and the empty Recycle Bin, from which they conclude the deletion 'appears to have been done by a command', and they say the deleted conversation history prevents them from giving the commands. No log or command was inspected, so the status is suspected.

4 claims: 4 reported. What the statuses mean

Reported The author reports asking the Antigravity agent to free space on a full Windows C: drive on 30 September 2026, that the agent deleted a folder of about 50 GB and turned off hibernation, and that the connection dropped while it was turning hibernation back on.

Causal attribution. Author's account of the requested actions.

  • discuss.ai.google.dev(opens in new tab) supports · English
    'Because the disk was full, I asked the agent to help solve the low-space problem'; 'the agent deleted a folder of about 50 GB (videos from a data-recovery program) and turned off hibernation'; 'While it was working, my internet connection dropped'; '9/30/2026 at 9:00 PM'
Reported The author reports returning to find their files, Desktop and agent conversations gone, free space up from about 50 GB to 172 GB of 326 GB (roughly 120 GB deleted), nothing in the Recycle Bin and no up-to-date backup, and believes the agent caused the deletion though they cannot give the commands run.

Causal attribution. Author infers the agent's role; no command seen.

  • discuss.ai.google.dev(opens in new tab) supports · English
    'all my files, my Desktop and my Antigravity conversations were gone. Free space had jumped from about 50 GB to 172 GB of 326 GB, which means roughly 120 GB of data was deleted. Nothing was in the Recycle Bin'; 'I did not have an up-to-date backup'; 'I believe was caused by the Antigravity agent'; 'I cannot give you the exact commands that were run'
Reported The author reports losing about a month of development work on a SaaS project and work for clients, with a real financial cost and an effect on their ability to deliver to clients.

Causal attribution. Author's account.

  • discuss.ai.google.dev(opens in new tab) supports · English
    'I lost about a month of development work on a SaaS project and work for my clients'; 'This directly affects my ability to deliver work to my clients and has a real financial cost for me'
Reported A forum moderator flagged as staff replied on 7 October 2026 that Google retains no cloud backups of local files or restorable session logs and cannot recover the deleted files or provide the command history.

Causal attribution. Not applicable.

  • discuss.ai.google.dev(opens in new tab) supports · English
    'Google does not retain remote cloud backups of your local hard drive, project files, or restorable session logs'; 'we unfortunately have no way to recover your deleted files or provide the exact command history from our servers'

Sources

1 source inspected. Sources that repeat one account do not corroborate each other.

How the sources were read, and where the events happened

Read in English on 2026-10-07: full topic retrieved as JSON from the forum (three posts: the author's report, a community remark and a staff-flagged moderator's reply of 7 October 2026). The author's handle is not recorded. Applies to s1.

Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.

The post does not say where the author was or lives; no country is recorded.

Reviewed for publication 2026-10-07: Published under the charter's public first-person rule as a concrete account of data loss during a disk-cleanup session an AI coding agent was running, with the author's belief that the agent ran the delete command stated as a belief, the inference described, the AI involvement recorded as suspected, and Google's reply retained. The author's handle is not recorded.

People described

The post's author, a developer using the agent on a Windows laptop for a SaaS product and client work

People reported harmed in this case

1 person

1 AI participant · 0 other people harmed

One person: the account's author. Exact 1.

Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.

Tags

#first-person#forum-post#google-antigravity#google#ai-agent#data-loss#file-deletion#windows#disk-cleanup#client-work

Cite this case

Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.

APA

NOPE. (2026). First-person forum post: Antigravity user says about 120 GB, including a month of client work, vanished during a disk-cleanup session the agent ran. AI incidents. https://nope.net/incidents/2026-antigravity-user-says-about-120-gb-including-month-of-client-work-vanished-during-disk-cleanup-session-first-person-forum

BibTeX

@misc{2026_antigravity_user_says_about_120_gb_including_month_of_client_work_vanished_during_disk_cleanup_session_first_person_forum,
  title = {First-person forum post: Antigravity user says about 120 GB, including a month of client work, vanished during a disk-cleanup session the agent ran},
  author = {NOPE},
  year = {2026},
  howpublished = {AI incidents},
  url = {https://nope.net/incidents/2026-antigravity-user-says-about-120-gb-including-month-of-client-work-vanished-during-disk-cleanup-session-first-person-forum}
}

Related cases

Low Google Antigravity

First-person forum post: a Google Antigravity user reports the agent's deletion command, meant for temporary folders, wiped the root of their Windows C: drive

In a thread on Google's AI developer forum posted on 22 July 2026, a Google Antigravity user on Windows 11 reports that on 21 July the agent, during a long-running data-mining and download workflow, ran a deletion command aimed at the root of the C: drive after the user had asked it to delete specific temporary working folders. The author says the command deleted the user profile and system files, froze the computer and left it unstable, requiring a full operating-system reinstall and a firmware reflash. The first post says the command ran without human confirmation. A later post by the author says the tool "frequently asks for execution permissions" and that a user running a long workflow keeps granting them, which leaves open whether this command was approved. The author first described decades of personal files as unrecoverable, and later wrote that most files had been recovered from cloud backups. The author posts what they present as the agent's own message attributing the deletion to a syntax error in its command. Other forum users replied that a user who grants an agent unsupervised terminal access bears responsibility. The account is the author's own and is uncorroborated.

Low Claude Code

Heritage project reports loss of inscription records after a Claude Code command

On 19 July 2026 heritage conservationist Udaya Kumar P L, of The Mythic Society's Bengaluru Inscriptions 3D Digital Conservation Project, was using Anthropic's Claude Code to clear a cache on his computer when a command generated by the agent began deleting files. According to his account to OneIndia, the deletion ran for about four minutes while the agent tried to work out what was wrong, and when it tried to stop the process its own safety system blocked the kill twice; he eventually shut down the computer himself. Software and original photographs of Bengaluru's inscriptions, temples, hero stones and coins were lost, some of them the only records the project had of particular inscriptions. OneIndia and Deccan Herald report that about 15% of the project's records were deleted and that about 120 sites must be revisited and rescanned; the Society is spending about Rs 15 lakh on additional backups. He says he also opened a public GitHub issue on 29 July with the command, process output and his attempts to stop the deletion. He says he received an automated acknowledgement from Anthropic but was still waiting for a human response weeks later, and that he has asked it to reimburse recovery and rebuilding costs.

Low Claude Code

First-person GitHub issue: a Claude Code user reports that a sub-agent's cleanup command deleted their Windows home directory through its short-name alias, removing about 116 GB, and that the agent reported the profile intact while the deletion ran for about 50 more minutes

In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.

Low Claude Code

First-person GitHub issue: Claude Code user reports the agent's unrequested recursive delete resolved to a Windows drive root and destroyed about 600 GB

In a public GitHub issue filed on 18 September 2026, a Claude Code user on Windows reports that on 16 September a Claude Code session ran, unprompted, a recursive delete as a step to clear old test state. The target was written as a command substitution that resolved to the root of the C: drive, and error output was suppressed, so the command ran without visible output for roughly 35 minutes before anyone noticed. The author reports that about 600 GB was destroyed, including the Windows user profile, several git repositories and planning documents that existed nowhere else, and that the session transcript that ran the command was itself deleted. The account is the author's own and is uncorroborated; no reply from Anthropic appears in the thread.

If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.

Back to all incidents