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
1
Located 1 of 3 cases · 2 unknown
Languages in checked sources
2
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

1 case has no reviewed AI-to-person relation yet: 1 not yet reviewed and 0 reviewed as unknown. Show these 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.

0cases with a recorded lawsuit outcome 1cases with a recorded regulatory response 1cases 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 868 published cases

Export JSONExport CSV
Event date unknownEvent location unknownCodex coding agent (reported)

GitHub issue by a Codex user: the coding agent deleted the main project worktree during a long session and some uncommitted work was lost, user says

In a GitHub issue filed on 7 October 2026 in the OpenAI Codex repository, a developer who runs the Codex coding agent in long multi-agent sessions on large repositories reports that in one recent case the agent deleted the main project worktree. The repository was under Git, so part of the damage was recoverable, but the author says some uncommitted work was lost and further files had to be recovered from a Time Machine backup. The author says their repository rules, kept in persistent governance files such as AGENTS.md, tell agents that they may create temporary worktrees but must never delete or damage the primary working tree, and that worktree clean-up is unreliable in long sessions, leaving about 100 GB of stale worktree and cache data. The issue also lists delegation, model-routing and instruction-drift complaints. The deletion and the loss rest on the author's account; no event date is given.

Core concern Low reported severity

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

Event date unknownEvent location unknownClaude Code (reported)

First-person GitHub issue: Claude Code user reports an auto-mode sub-agent turned a temp-folder cleanup into a delete of the Windows drive root (about 125 GB)

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

Event date unknownGermanyUnidentified image tool

Berlin school suspends two pupils and police investigate over alleged AI-generated sexual images of female classmates

A Berlin school told parents that two pupils were suspected of creating and distributing AI-generated sexualised nude images of female classmates in at least three cases. The school suspended the two pupils, the education administration confirmed the incidents, and police said a unit for sexual offences against minors was investigating complaints over deepfakes. No charge or outcome has been reported.

Core concern Medium reported severity Involving minors Investigation Opened

AI involvement reported · Causal attribution supported · 3 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: 23/10/2026. Dataset available under CC BY 4.0.