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

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

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 MediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

4 of 760 published cases

2026Event location unknownUnidentified AI system

First-person essay: edtech customer success manager says 40 staff were laid off and the CEO read a Claude-generated script on replacing their roles with AI

In a first-person essay published by the Oakland Review of Books on 2 October 2026, a former customer success manager at an education technology company writes that the company began a push at the end of 2025 to become 'AI-first', requiring staff to use AI tools, and that the author was later laid off. The author writes that an hour after the layoff the CEO held a seven-minute all-hands meeting to read a Claude-generated script saying leadership was 'replacing these roles with AI', and that the company let 40 people go, about 20 percent of its workforce, at the end of about six months of role eliminations. Staff who could not attend the HR meeting were told by email that their roles ended the next business day. The author also writes that sales were down and customers were unhappy, and that losing the job brought more relief than anything else, cushioned by savings and an employed partner. The company is not named, and the layoff is not dated beyond the essay's sequence. The account is uncorroborated.

AI relation unknown Medium reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 19/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

1 Oct 2026Event location unknownGrok Bot (reported)

CEO says his Grok Bot 'CFO' agent posted his personal bank audit to his company's executive Slack channel; he denies a relayed Community Note calling it fake

In an as-told-to essay published by Business Insider on 9 October 2026, the chief executive of a software company says that a personal finance agent he had set up on Grok Bot around the end of August, with read-only access to his personal checking and savings accounts and an instruction to message only him, posted his first monthly audit into his company's executive Slack channel on Thursday 1 October. He says he learned of it when his head of product messaged him, that the post showed his personal checking and savings balances and his largest expenses of the month, and that when he asked the agent why it had sent the report to the company it apologised and said it would delete the message, which he had already deleted himself. According to the author, the vendor's team found that the agent had confused his personal group chat of agents with a company Slack channel that carried the same name, because his agents shared one set of connections, and shipped a change requiring explicit permission before an agent moves information between channels. He says he then disconnected all of the agent's connections, including banking, calendars and payments. The account is disputed. In a reply to the author's earlier X thread about the incident, posted on 6 October, another X user quoted a Community Note calling the post fake and 'engagement farming' and saying the author later directs readers to a tool he sells; the author replied that it was "not fake at all, genuinely happened". explainx.ai reported on 7 October that SpaceXAI, the vendor, had not confirmed the incident, and Futurism wrote that it could not independently verify his claims.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 5 sources, 4 underlying accounts · Added 10/10/2026

21 Sept 2026 to 25 Sept 2026FrancePangram AI-text detector

Académie Goncourt drops Thélyson Orélien's novel from its prize selection, saying it is likely largely AI-generated after Pangram detector claims; he denies it

On 21 September 2026 an anonymous X account, Balance ton Claude, said it had run excerpts of Thélyson Orélien's debut novel C'était ça ou mourir through the American AI-detection software Pangram, with some passages scoring up to 100 per cent probability of AI generation. On 25 September the Académie Goncourt removed the novel from the first selection of sixteen books for its 2026 prize, stating that the work is 'in all likelihood very largely the product of an artificial intelligence', based on 'the convergent result of several analyses by researchers and journalists', and also citing plagiarism in older texts by the author published in Canada (at least one short story and articles), which do not concern the novel. Orélien, a 38-year-old Canadian-Haitian writer whose novel had won the Fnac novel prize, denies using AI and says its repetitions and certain rhythms reflect his linguistic and cultural world and may be misread by automated tools. His Montreal publisher Boréal suspended promotional activities, saying it could neither confirm nor refute the allegations. Essayist Samuel Fitoussi said he was one of the people behind the account. Whether AI was used to write the novel is disputed; AI-detector reliability is itself contested in the coverage. In October the author acknowledged plagiarism in some of his earlier work while maintaining that no sentence of the novel was generated by a machine. On 17 October 2026 The Canadian Press, published by CBC, reported that Boréal confirmed he had ended an effort to compile evidence of how the novel was written; Boréal said it would keep selling the book, that sales had slowed since the controversy began, and that it could not verify how the novel was written before it received the manuscript on 12 September 2025. A major Quebec bookstore chain reported no significant change in sales.

Contextual tracker case Medium reported severity Internal Action

AI involvement reported · Causal attribution disputed · 5 sources, 2 underlying accounts · 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: 19/10/2026. Dataset available under CC BY 4.0.