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 is wider: it also records consequential decisions and claims about people. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
2
Countries with reported events
1
Located 1 of 2 cases · 1 unknown
Languages in checked sources
1
Recorded for 2 of 2 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 Low
More filters: AI relation, use, setting, sources and responses
Clear filters

2 of 404 published cases

9 May 2026United StatesWaymo Driver

San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026)

At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider told the San Francisco Chronicle and NBC Bay Area that two men then struck the windshield and windows and climbed onto the car while it stayed stationary. The rider says Waymo support staff on the car intercom declined to move it, saying it was obstructed, although the rider saw nothing blocking it, and remembers about 10 minutes before the men left. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police. The Chronicle reports that officers arrived at 3:46 a.m. The police report, as described by both outlets, identifies Waymo as the victim of malicious mischief and the rider as a witness. Police officials say the rider told officers of no injury. The rider later felt pain behind an ear that the rider believes came from glass, and sought therapy. Waymo spokespeople did not comment on the account in the reporting, and Waymo told the rider in an email that it was unable to access any footage without proper legal justification. The account is the rider's as reported by the Chronicle (16 July 2026) and NBC Bay Area (16 July 2026). The police report was not inspected and is known only through the outlets' descriptions.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 3 sources, 2 underlying accounts · Added 29/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

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: 30/09/2026. Dataset available under CC BY 4.0.