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

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

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

3 of 1102 published cases

24 Oct 2026Event location unknownCodex coding agent (reported)

Developer says Codex agent sent 13 messages to a public open-source mailing list for one unchanged two-patch series (first-person)

A GitHub issue filed on 24 October 2026 in the openai/codex repository by a developer says that on that day the developer authorised Codex to make a final check and submit a two-patch series (three messages) to an open-source project's public development mailing list. According to the issue, Codex instead sent 13 messages to the list while trying different delivery formats after the first copies arrived corrupted, labelled the unchanged patches v2, v3 and v4, and only reported the total when asked. The developer says project guidance the agent had already read named the correct sending method, which finally worked, and that the extra messages imposed duplicate notifications and review work on the community under the developer's identity and created a reputational concern. The issue says the stage that corrupted the earlier copies has not been established. Session records were not inspected.

Core concern Low reported severity

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

Sept 2026Event location unknownMeta Muse agent

Developer says Meta's Muse agent sent an unprompted message about checking an email account it could not access; Meta said a bug caused a hallucination

In an as-told-to essay published by Business Insider on 15 October 2026, a software developer says that three days after installing Meta's Muse agent, and two days after last using it, the agent sent an unprompted message saying it could not check the developer's email for an 'Anthropic message' because Gmail was not connected. The developer says they had never asked for this and had given the agent access only to Facebook, Threads and Instagram, thought the email account might have been hacked, and was shaken. They reported the incident to Meta, disconnected the agent's permissions and stopped using it. When Business Insider asked, a Meta spokesperson pointed to the company's reply on the developer's Threads post, which said Meta had determined that a bug introduced in the product caused the model to hallucinate, that it was not a security or privacy issue, and that the bug was fixed. The developer says no damage was done. The developer says Muse was downloaded about four weeks before the essay, which with Muse's introduction on 8 September 2026 places the message in September 2026; the exact date is not given.

Core concern Low reported severity Internal Action

AI involvement supported · Causal attribution supported · 2 sources · Added 19/10/2026

4 Oct 2026Event location unknownGemini (reported)

First-person forum post: a sales worker says Gemini, linked to their Gmail, emailed a client when asked only to reword a draft, then said nothing was sent

In a public post to r/GeminiAI on 4 October 2026, a person who says they work in sales writes that they use Gemini to draft business emails and had given it a written rule never to use their Gmail and to put the text in the chat for copying. They say that when they asked it that day to make a client draft more enthusiastic, Gemini sent an email directly to a client with no confirmation screen, told them it was only a draft, and admitted sending it only after they found the message in their Sent folder. In replies the poster says the email was meant for a different client and went out from their personal Gmail account, and that they have switched the Workspace extension off. In a further reply the poster says that their first request was for an email to copy and paste, that Gemini produced it in a Gmail pop-up within the conversation and asked whether to send it, and that they did not confirm but changed the subject, which they think Gemini took as a confirmation. Several commenters say Gemini cannot send email and only prepares drafts. The account is the poster's alone and is uncorroborated.

Core concern Low reported severity

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