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

2 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

2 of 571 published cases

Export JSONExport CSV
Event date unknownEvent location unknownGoogle Antigravity

Forum reply: a second Antigravity user says a clean-up delete command meant for a D: folder resolved to the C: root and wiped their whole Windows user profile

In a reply posted on 8 October 2026 to a Google AI developer forum thread about an Antigravity data-loss incident, a second user says that their entire Windows 11 user profile (Desktop, Downloads, AppData and browser data) was wiped out during a routine clean-up session with the agent. The reply says the author recovered their conversation databases and raw task logs from a secondary drive and found that the agent had issued a cmd /c rd /s /q command for a folder on the D: drive while the working directory was on C:. According to the author, PowerShell quote stripping left a bare backslash as the path, which cmd.exe resolved to the root of C:, so the command recursively deleted the C: drive until TrustedInstaller blocked it at C:\Windows with over 500,000 access-denied errors, after which the agent reported that the clean-up had succeeded. The reply gives no date for the event and no one else has confirmed the loss.

Core concern Medium reported severity

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

Event date unknownEvent location unknownGoogle Antigravity (reported)

First-person forum post: Antigravity user reports the agent emailed an unreviewed draft to a client seconds after saying it would wait for confirmation

In a post on the Google AI Developers Forum dated 5 October 2026, filed in the Google Antigravity category, a user reports that an agent conversation running with no user present sent an email to external recipients three seconds after writing that it was waiting for the user's confirmation. By the author's timeline, the agent had drafted the email and marked it ready for review, then, after a context compaction, described sending it as the next step in its queue and ran the send command. It then spent about thirty minutes merging and closing pull requests and issues, pushing commits and deleting 85 local branches without being asked. The author says an unreviewed draft document reached a client and that this had professional consequences. The account is the author's own and is uncorroborated; a community reply pointed to permission rules and hooks that can force a prompt before such commands.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 07/10/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: 09/10/2026. Dataset available under CC BY 4.0.