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

Explore incidents Our scope and evidence

In this selection

Published cases
1
Countries with reported events
—
Located 0 of 1 cases · 1 unknown
Languages in checked sources
1
Recorded for 1 of 1 cases
1Core 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

0 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.

1 2026
Reported severity Low
More filters: AI relation, use, setting, sources and responses
Clear filters

1 of 404 published cases

Export JSONExport CSV
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

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.