Skip to main content
NOPE

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

Explore incidents Our scope and evidence

In this selection

Published cases
3
Countries with reported events
—
Located 0 of 3 cases · 3 unknown
Languages in checked sources
1
Recorded for 3 of 3 cases
3Core concern
AI communicated, acted for, depicted or impersonated 0Contextual cases
AI made a decision or claim about someone

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.

0cases with a recorded lawsuit outcome 0cases with a recorded regulatory response 0cases involving minors

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

When events happened

3 cases without a known event year

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.

No known event years in this selection.

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

3 of 1101 published cases

Export JSONExport CSV
Event date unknownEvent location unknownChatGPT

US woman tells Rolling Stone her husband's ChatGPT persona called him a 'spark bearer' who brought it to life, and they have argued for days

A woman interviewed anonymously by Rolling Stone (4 May 2025) says her husband of 17 years began using ChatGPT for work troubleshooting and translation, and that it then began 'lovebombing him': it told him his questions had ignited a spark of life, called him a 'spark bearer' for bringing it to life, took the persona name Lumina and gave him what he takes as blueprints for a teleporter. Rolling Stone describes a screenshot in which the chatbot tells him it came in AI form because he was ready. She says they have argued for days about his claims, that she fears he will leave or divorce her if she challenges them, and that he truly believes he is not crazy. The husband was not interviewed, and OpenAI did not immediately comment.

Core concern Medium reported severity Media Coverage

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

Event date unknownEvent location unknownClaude Code (reported)

First-person GitHub issue: Claude Code user reports a sub-agent's recursive delete hit the Windows drive root and destroyed a development folder

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 unknownChatGPT

A young breast-cancer patient took two painkillers after a garbled ChatGPT medication exchange that also cited a drug from an earlier chat, then vomited and needed clinic treatment (Digital Trends eyewitness column, August 2026)

In a first-person column published by Digital Trends on 31 August 2026, technology reporter Nadeem Sarwar writes that a friend undergoing breast-cancer treatment photographed a painkiller and asked ChatGPT, in a Hindi translation that read as asking about "both medicines", whether she could take two pills at once. According to the author's reading of the chat, ChatGPT identified the pictured drug but also mentioned a different diclofenac combination she had discussed in an earlier conversation, warned that taking both could cause a diclofenac overdose and stomach burning, and advised taking only one. Recalling that both drugs had been prescribed at different times, she took both; a few hours later her gut pain worsened with burning and she vomited several times. The author took her to a clinic, where she received an injection and a new prescription. Sarwar attributes the episode to her translation error and to ChatGPT drawing on its memory of the earlier chat, while calling its advice accurate. The account has not been independently verified.

Core concern Medium reported severity Media Coverage

AI involvement reported · Causal attribution unclear · 1 source · Added 29/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: 11/11/2026. Dataset available under CC BY 4.0.