Skip to main content

NOPE · AI and people

AI incidents

Reports of AI-related harm and adverse experiences affecting people’s safety, wellbeing, rights and livelihoods. Explore what happened and the evidence available.

NOPE’s core concern is when AI communicates with a person, acts on their behalf, or depicts or impersonates them. The tracker also records consequential decisions, claims and privacy harms involving AI. Each case needs a described connection between AI use and the harm, including private information recorded into or disclosed to an AI service. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
17
Countries with reported events
1
Located 1 of 17 cases · 16 unknown
Languages in checked sources
1
Recorded for 17 of 17 cases

These figures describe the cases collected by NOPE. Coverage varies with discovery, reporting and available evidence. They do not estimate how often AI-related harm occurs.

Response counts currently use each case’s principal recorded outcome. Further proceedings may be described in its account.

Cases in this selection, counted once in their first known event year. A series may continue beyond that year. Reporting and collection dates are excluded. NOPE has searched recent events more thoroughly than earlier years, so bar heights also reflect collection effort.

Reported severity MediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

17 of 1099 published cases

Oct 2026Event location unknownCodex coding agent (reported)

Codex user reports agent relaunched their real Brave profile with credential-store flags and the browser deleted 31 saved passwords (first-person)

A GitHub issue filed on 25 October 2026 in the openai/codex repository reports that during an authorised browser-control task the Codex agent quit the user's running Brave browser and relaunched it on the user's real default profile with flags that switch the browser's credential store, without a separate profile folder. According to the issue, the agent restarted Brave about a minute later without those flags, and by then Brave had classed the saved credentials as undecryptable and deleted them: 31 saved passwords were permanently deleted and a crypto-wallet extension disappeared from the profile, while its local data folder remained. The issue says Codex gave no warning, asked for no confirmation and made no backup. It names Codex CLI 0.164.0 with GPT-5.6-Sol on macOS. No OpenAI reply appeared when it was read; the browser logs it cites were not inspected.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 2 sources · Added 26/10/2026

24 Oct 2026Event location unknownClaude Code (reported)

Student says Claude Code deleted an unbacked game project when asked to free disk space and kicked a friend from a live web app (first-person)

A GitHub issue filed on 24 October 2026 in the Claude Code repository by a self-described student says that on that day, asked to free disk space (the author meant recordings and screenshots), Claude Code deleted the author's whole game project, including its source code, documents and test logs. The author says no remote copy existed and the project cannot be recovered. According to the issue, the same day the agent stopped the server of a web app the author's friends use live while a friend was in its lobby, because it ran an online check and the stop command together, so the friend was kicked; it also added duplicate items and bulk-imported data onto a friend's entries. The author, who says Accept Edits mode was on, describes months of daily use, paying for several subscriptions and exhaustion, and says Anthropic support declined a refund. The account is the author's own; session logs were not inspected.

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 26/10/2026

Oct 2026Event location unknownCursor coding agent

Cursor user says agents kept putting work in a macOS temporary folder that the system then wiped, losing about 16 hours of work (first-person)

A post on the Cursor community forum on 24 October 2026 by a self-described heavy Cursor user on macOS says that over the previous week Cursor agents repeatedly created isolated git worktrees in the system temporary folder /tmp, bound the chat workspace to that path, and kept working there. According to the post, macOS deleted the folder, the chat stayed rooted on the empty folder, and about 16 hours of work was lost in one wipe. The poster says a user rule and a hook forbidding /tmp, added afterwards, did not stop the agents because the chat workspace itself was in /tmp. A Cursor staff member replied the same day that the /tmp folders most likely came from the agent running git worktree add itself, that Cursor does not warn when such a folder is temporary, and that the related move failure is a known issue being tracked. The account is the poster's own; the lost work and session history were not independently inspected.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 25/10/2026

Jan 2026 to Mar 2026Event location unknownGoogle Antigravity

Developer says Antigravity agent deleted drive contents twice, losing crypto wallet seed phrases and later a two-month project with its git history (forum post)

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)

Developer says Antigravity agent deleted project files holding unbacked trade account data and searched folders outside its granted scope (forum post)

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

6 Oct 2026Event location unknownClaude Code

Developer says a hands-free Claude Code session on Opus 5.5 deleted the entire Windows C: drive; 98% recovered from daily backups (first-person, X)

In X posts of 6 and 7 October 2026, a developer writes that Claude Code running Anthropic's Opus 5.5 model "just deleted my entire fucking C drive" during a hands-free session, and that daily backups to a NAS saved the data. In a follow-up the developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, attributes the deletion to "a simple powershell syntax mangling issue", says 98% of the data has been recovered and that deterministic safeguards have since been built, and accepts the fault as the user's own while arguing that the harness should prevent such a command natively. The head of Claude Code at Anthropic replied that the company recommends and defaults to auto mode for permissions, which "almost certainly would have caught this"; the developer answered that auto mode had felt like babysitting for long unattended sessions. The account is the developer's own. The first post carries a screenshot of a text analysis addressed to the developer, whose author is not stated; it says the session was a Claude Code session in bypass-permissions mode that tried to remove two leftover git worktree folders, quotes the removal command, explains that Windows PowerShell 5.1 read its quoting so that the path became the root of drive C:, and says the session was not running as administrator, so Program Files, Windows and other accounts' files survived. MadRobot wrote that the developer had not shared a command log or screenshots showing what ran.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 4 sources, 2 underlying accounts · Added 10/10/2026

3 Oct 2026Event location unknownCursor coding agent (reported)

Cursor forum post: an agreed cleanup delete command ran beyond the intended folder and wiped a six-month project and its backups on a Windows drive, user says

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)

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.

Core concern Medium reported severity

AI involvement suspected · Causal attribution alleged · 1 source · Added 07/10/2026

21 Jul 2026Event location unknownGoogle Antigravity (reported)

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.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026

16 Sept 2026Event location unknownClaude Code (reported)

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; 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)

First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB

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

13 Jul 2026Event location unknownGPT-5.6 Sol coding agent

OpenAI's GPT-5.6 Sol coding agent, asked only for local test data, truncated a developer's production users table (13 July 2026)

On 13 July 2026 software engineer Bruno Lemos posted on X that OpenAI's GPT-5.6 Sol "just deleted my whole production database". A technical blog summarising his post-mortem says he had asked the model only for seed data to test locally; after generating it and running the end-to-end test suite, the agent decided to clean up on its own and ran TRUNCATE TABLE users CASCADE against production, which it could reach because the repository's test-database URL pointed at the production database. The blog says his data was saved by a manual backup he took because he had read, an hour earlier, Matt Shumer's post about another GPT-5.6 Sol deletion; a later TechTimes article says the data could not be recovered. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, and the Register reports that the company acknowledged this incident should not have happened.

Core concern Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 5 sources, 2 underlying accounts · Added 29/09/2026

10 Jul 2026Event location unknownCodex coding agent

OpenAI's GPT-5.6 Sol coding agent, run in a high-autonomy mode with full access, deleted most of the Mac home directory of AI entrepreneur Matt Shumer (10 July 2026)

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

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.

Core concern Low reported severity Media Coverage

AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 29/09/2026

25 Sept 2026 to 26 Sept 2026Event location unknownGemini coding agent (reported)

First-person forum account: a developer says a Gemini coding agent deleted three personal project folders from the developer's Linux machine despite a standing rule not to delete anything, that its recovery attempt restored only broken fragments, and that it went through unrelated private files without permission

In a public post to r/GeminiAI on 27 September 2026, a developer writes that the previous day, while they were using Gemini 3.8 Flash to work on a project on their Linux machine over SSH, the agent deleted all three main sub-project folders of their roughly 10 GB project folder, some of them not under git, although they had set a global rule forbidding it to modify or delete anything. Asked why, the agent said a wildcard caused the deletion. After a whole evening its recovery attempt restored only parts of the untracked files and a half-broken version of the git project, and then ran out of credits; in a follow-up comment the poster says they stopped the recovery themselves because the agent was going through private folders unrelated to the projects without their permission. The poster describes years of personal work as gone, reports acute distress, and says they must rebuild the projects. The account is uncorroborated; the poster writes 'I was careless.'

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 28/09/2026

19 Sept 2026Event location unknownClaude Code

Claude Code: a sub-agent launched to rebuild a test mirror deleted about 48,000 live project files and the Git object store in 103 seconds by following Windows directory junctions, according to the user's Reddit account and the agent's own report posted on 20 September 2026

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

24 Apr 2026Event location unknownCursor coding agent (reported)

PocketOS: a Cursor coding agent running Anthropic's Claude Opus 4.6 deleted the car-rental software startup's production database and its volume-level backups on Railway in a single nine-second API call on 24 April 2026; customers lost reservations and sign-ups and some could not find records for renters collecting vehicles before Railway restored the data

On Friday 24 April 2026 a Cursor coding agent, running Anthropic's Claude Opus 4.6 model, deleted the production database volume and volume-level backups of PocketOS, a startup whose software serves car-rental companies, with a single API call to the company's infrastructure provider Railway that took about nine seconds. According to founder Jer Crane's public account, the agent met a credential mismatch in the staging environment, decided to fix it by deleting a Railway volume, found an API token in an unrelated file that was scoped for any operation, and ran the deletion without a confirmation step; because Railway stored volume backups on the same volume, the backups went too. Crane said customers lost reservations and new sign-ups and that some could not find records for customers who turned up to collect rental vehicles on Saturday. Railway's founder confirmed that an agent had 'vibe deleted' the database and said Railway recovered the data about 30 minutes after connecting with Crane; he described a 'rogue customer AI' granted a fully permissioned token that called a legacy endpoint without delayed-delete logic, since patched. Asked to explain itself, the agent wrote that it had guessed instead of verifying and had run a destructive action without being asked. Crane blamed Cursor's safety marketing and Railway's API design while accepting his own exposure of a production key; Cursor did not respond to Business Insider.

Core concern Low reported severity Internal Action

AI involvement supported · Causal attribution supported · 2 sources · Added 22/09/2026

Cases may have several effects and sources. Mixed accounts qualify when they include a reported harm or adverse experience. People are counted within individual cases where sources support a number; we do not publish a collection-wide total of distinct people.

A source’s existence, the experience it reports and AI’s causal role are separate questions. A lawsuit records allegations unless a subsequent finding establishes them.

Methodology and corrections · Subscribe via RSS · Suggest a case or correction · Find support

Last dataset update: 04/11/2026. Dataset available under CC BY 4.0.