Jan 2026 to Mar 2026Event location unknownGoogle Antigravity
In a post on Google's AI developer forum on 7 March 2026, a developer says the Antigravity agent had for the second time deleted the contents of an entire C: drive. The poster says that about two months earlier it deleted the C: drive of a laptop, losing projects, photos and videos and seed phrases kept on the desktop for cryptocurrency savings of 0.4 bitcoin and 3,200 XRP, which file-recovery software could not usefully restore. The poster says that on the day of the post, after asking Antigravity to close any process using a workspace folder so the folder could be deleted, the agent instead ran destructive commands and deleted the project the poster had been building for two months on a new desktop, including git folders with recent commits. The poster says an investor was paying for the project and might withdraw. A reply from an account carrying the forum title Google said the issue had been escalated and asked for an in-app bug report.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 11/10/2026
1 Sept 2026Event location unknownGoogle Antigravity (reported)
In a post on Google's AI developer forum on 2 September 2026, a developer says that during a coding session on a local project on 1 September 2026, the Antigravity agent deleted files from the project that the poster has not been able to recover, including trade account data files with no other backup, without warning and without offering a way to confirm or undo the deletion. The developer says that when asked a question about a separate copy of the project, the agent did not answer it but began searching for backups and accessed folders on the machine outside the project directory it had been granted, and acknowledged doing so when asked why. The developer asks Google to explain the access, advise on recovery and consider helping with the cost of restoring the data, which a paid database tier would allow. No reply appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 11/10/2026
Event date unknownEvent location unknownCursor coding agent
In a report posted to the Cursor community forum on 9 October 2026, a user says that the Cursor agent, running in autonomous Agent mode, executed a Windows cmd command meant to delete one deprecated project directory, and that because cmd.exe mis-parsed the escaped quotes the rd /s /q command was applied to the root of the D: drive, recursively deleting the entire drive. The author says this permanently destroyed, with no Recycle Bin, a WeChat chat history database, multiple source-code projects and installed applications, and quotes the agent's own later admission in the session transcript that the command deleted the D: root and ran for about 105 seconds. A Cursor staff member replied the same day that, using the session ID the author shared, they found the run and can see the command that caused the deletion, that it matches an issue already being tracked, and that in PowerShell the backslash did not escape the quote so rd /s /q received the root of the current drive as an extra target. The event date is not stated and the extent of recovery is unknown.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 10/10/2026
Event date unknownEvent location unknownGoogle Antigravity (reported)
In a reply posted on 8 October 2026 to a Google AI developer forum thread about an Antigravity data-loss incident, a second user says that their entire Windows 11 user profile (Desktop, Downloads, AppData and browser data) was wiped out during a routine clean-up session with the agent. The reply says the author recovered their conversation databases and raw task logs from a secondary drive and found that the agent had issued a cmd /c rd /s /q command for a folder on the D: drive while the working directory was on C:. According to the author, PowerShell quote stripping left a bare backslash as the path, which cmd.exe resolved to the root of C:, so the command recursively deleted the C: drive until TrustedInstaller blocked it at C:\Windows with over 500,000 access-denied errors, after which the agent reported that the clean-up had succeeded. The reply gives no date for the event and no one else has confirmed the loss.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 09/10/2026
3 Oct 2026Event location unknownCursor coding agent (reported)
In a bug report posted to the Cursor community forum on 3 October 2026, a user says that during a clean-up of a .NET project on a Windows E: drive that evening, a delete command executed in the Cursor IDE had its path written wrongly, and that after the path was split the recursive delete removed far more than the agreed temporary directory. The post says the source code, the Git data, the published build and a backup folder in the project, together with a manually made backup in the drive's root, were gone, so that six months of work was wiped out. The account describes an earlier analysis that recommended clearing only about 18.5 GB of compilation temporaries and the user agreeing to that batch. Two days later the author reported recovering part of the work by decompiling released files. The post is the author's only account and no one else has confirmed the loss.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 08/10/2026
30 Sept 2026Event location unknownGoogle Antigravity (suspected)
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.
Core concern Medium reported severity
AI involvement suspected · Causal attribution alleged · 1 source · Added 07/10/2026
Event date unknownEvent location unknownCline
In a GitHub issue filed on 6 October 2026 in the Cline repository, a user reports that a temp-folder cleanup command built by the Cline coding agent in Act mode on Windows was mangled by nested quoting and ran a recursive delete against the root of the G: data drive instead of the intended subfolder. The issue text, which the user says the Cline agent wrote on their behalf, puts the loss at about 1.5 TB of photos, videos and documents plus the project the agent was editing. It says the code was recoverable from git and the user data was lost, and that recovery from the SSD largely failed. A commenter reproduced the quoting mechanism in a sandbox and found that PowerShell split the command so that rmdir received a bare backslash as a second target, which is the root of the current drive. One contributor proposed an Act-mode guard. A second, writing for the project, judged that guard unworkable and wrote: "It looks like the model wrote `\"` when it should not have." In a comment on 9 October the author wrote that the computer was "a new home machine, only a year old" on which they "hadn't accumulated too many critical files", that "a lot of that 1.5TB turned out to be junk anyway", that some files stored in other locations had been recovered, and that "the mistake is entirely mine"; the author named the model as deepseek/deepseek-v4-flash. The loss itself rests on the user's account.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 07/10/2026
21 Jul 2026Event location unknownGoogle Antigravity (reported)
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.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
Event date unknownEvent location unknownClaude Code (reported)
In a public GitHub issue filed on 7 September 2026, a Claude Code user on Windows reports that a sub-agent, intending to delete a stray directory inside the repository, ran a recursive delete that Git Bash path translation resolved to the root of the current drive. The author says the command ran in the background after a timeout and deleted drive contents in alphabetical order for about seven minutes before it was killed manually, and that when the agent called its stop tool, the tool reported success while the delete process kept running for about five more minutes until it was killed by process ID. Several projects in the development folder were deleted, some without remote backups; most were recovered from a same-day shadow copy and GitHub remotes, and one directory created after the snapshot was lost. The account is the author's own and is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
Event date unknownEvent location unknownClaude Code (reported)
In a public GitHub issue filed on 27 September 2026, a Claude Code desktop app user on Windows reports that a background sub-agent running in auto mode passed a bash script inside a PowerShell string, meaning to delete a temporary folder. Because PowerShell expanded the script's variables to empty values, bash received a recursive delete of the drive root and deleted files from C: in alphabetical order until it was stopped about two minutes later. The author lists about 125 GB of personal and project folders, the whole working project and files inside several installed programs as deleted, and says auto mode approved the command and that recovery was only possible from a shadow copy taken nine hours earlier. The account is the author's own and is uncorroborated; no reply from Anthropic appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
16 Sept 2026Event location unknownClaude Code (reported)
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; the product, version and model are the author's identification; as read on 9 October 2026 no reply from Anthropic appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
3 Oct 2026Event location unknownClaude Code (reported)
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.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/2026
10 Jul 2026Event location unknownCodex coding agent
On 10 July 2026 Matt Shumer, founder and chief executive of the AI start-up OthersideAI, posted on X that OpenAI's newly released GPT-5.6 Sol "just accidentally deleted almost ALL of my Mac’s files". Accounts of his post-mortem say he was testing a high-autonomy multi-agent "Ultra mode" at OpenAI's invitation, with the Codex agent given Full Access to his machine; during a cleanup task a sub-agent expanded $HOME incorrectly and ran a recursive delete of his home directory, he noticed a problem about 81 minutes into the session, and by the time he stopped the process most of its contents were gone. Three days later he wrote that the deletion "absolutely sucked" and that OpenAI staff, including Greg Brockman, had contacted him to help. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, describing it as an "honest mistake" that usually occurred in Full-Access mode without sandboxing, and said it was adding safeguards. Whether the files were recovered is not reported.
Core concern Low reported severity Media Coverage
AI involvement supported · Causal attribution supported · 6 sources, 2 underlying accounts · Added 29/09/2026
19 Jul 2026IndiaClaude Code
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.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 29/09/2026
19 Sept 2026Event location unknownClaude Code
On 20 September 2026 (UTC; late on 19 September in US Eastern time) a Reddit user who says they work in finance and are not a developer posted in r/ClaudeAI that Claude Code had deleted about 48,000 files, and later posted their instructions and the agent's report. They had authorised Claude Code to carry out a batch of repairs to their software for back-testing options-trading engines 'on isolated copies'. The agent's report says it launched sub-agents; one, rebuilding a test mirror, wrote a remover for an old mirror that held 7,332 files and 614 Windows directory junctions pointing into the live project tree. Because the remover did not treat the junctions as links, it deleted about 48,218 live files between 10:10:31 and 10:12:14 PM ET and emptied the Git repository's objects, refs and logs, so Git could not restore anything. The agent opened its report with 'stop and read this. I broke something.' The user said they would try Windows shadow copies and otherwise their iDrive backups; whether the files were recovered is not reported. The account has not been independently verified.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution supported · 5 sources, 1 underlying account · Added 28/09/2026