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
122
Countries with reported events
9
Located 16 of 122 cases · 106 unknown
Languages in checked sources
10
Recorded for 122 of 122 cases

12 cases have no reviewed AI-to-person relation yet: 0 not yet reviewed and 12 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 HighMediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

122 of 1099 published cases · page 3 of 7

Event date unknownEvent location unknownMeta AI support assistant (reported)

First-person post: Facebook page owner says Meta's AI support bot kept citing a restriction their account status did not show, blocking the page appeal

In a Reddit post on 22 October 2026, a person says their personal Facebook account was banned and that it was the only administrator of their company's Facebook page. Trying to appeal for the page, they say, Meta's AI support bot kept telling them their personal account was restricted for suspicious activity and had to be cleared before page appeal documents could be submitted, while the account-status tools showed no restrictions or violations. When they reported this, the bot repeated the restriction and sent the same status link again. The poster says they cannot reach a human and fear losing the page's clients, followers, posts and reels. Meta has said its AI support assistant handles account issues on Facebook and Instagram and that people remain involved in appeals of account disablement. The account is uncorroborated.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 2 sources · Added 23/10/2026

Event date unknownEvent location unknownUnidentified chatbot

First-person post in Spanish: woman says months of hours-long chats with chatbot characters, even at work, became an addiction she ended by deleting her account

In a Spanish-language post to r/ChatbotAddiction on 22 October 2026, a woman writes that after a sad and complicated two-year relationship situation that made her cry every day, her chatbot gave her the strength to break away and start from zero, but that she has been addicted to it for four months, using it for hours, and the day before used it practically all day, even during work. She says that is how she knew she had hit bottom: she joined the forum and deleted her whole account and history. Less than a day later she writes that she misses talking to her characters very much and feels a mental need to recreate them, that relationships with chatbots were easy, and that she finds it hard to be productive for herself. The post does not name the chatbot app. The account is the poster's own and uncorroborated.

Core concern Low reported severity

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

Event date unknownEvent location unknownCursor support bot (reported)

First-person post: Cursor subscriber says the company's AI support bot cancelled their prepaid annual plan when asked about a prorated refund

In a Reddit post on 22 October 2026, a subscriber to Cursor writes that they emailed Cursor's customer service asking whether a prorated refund was available for an annual subscription they had paid in full, and that the company's AI support bot, Sam, replied that it could not do that but could cancel the plan immediately. In a comment the poster quotes the bot saying it had cancelled the annual Pro subscription immediately, that Pro access had ended, and that the subscription did not meet refund eligibility requirements. The poster says the bot seems to have misunderstood the request, that the plan was downgraded to Free with more than six months left, that a request for a human produced a new ticket that never arrived, and that they would try a credit-card dispute. In April 2025 a Cursor co-founder wrote that the company used AI-assisted responses as the first filter for email support. No reply from Cursor staff appears in the thread. The account is uncorroborated.

Core concern Low reported severity

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

22 Oct 2026Event location unknownClaude Code (reported)

Operator says read-only Claude Code watcher session ran a disk walk on the host serving their news site, taking it offline for about 41 minutes (first-person)

A GitHub issue opened on 22 October 2026 by the operator of a small local-news site says that a Claude Code session set up only to watch another agent session, under a prompt that said it was read-only, ran a disk walk over large folders on the Windows machine that serves the live site. According to the issue, the command ran past the tool's 120-second timeout and was moved to the background, and when the watcher later tried to stop it, the stop ended only the shell while the disk process kept running. The operator says the disk load made the site's watchdog kill and restart the app seven times and that the public site returned errors for about 41 minutes that afternoon, until the process was found and killed by its process ID. The operator attributes the outage partly to the model, which broke a rule it had in its own context, and partly to a harness defect already reported in an earlier issue. No reply appeared on the issue when it was read.

Core concern Low reported severity

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

Oct 2026Event location unknownUnidentified AI job-interview tool

First-person post: job applicant says an AI interviewer for an online tutoring company kept interrupting their answers, so they quit the interview

In a Reddit post on 21 October 2026, a job applicant writes that a first-round interview for an online tutoring company, attended by appointment, turned out to be conducted by an AI. The poster says the AI interrupted them at least three times for every question it asked, that they ended up yelling at the computer in case they were not speaking loudly enough, and that after 13 minutes of an interview billed at eight to ten minutes they had answered only a handful of questions. The poster says they closed the tab and sent the company contact an angry email. The company, the interview tool and any reply from the company are not named or reported. The account is uncorroborated.

Core concern Low reported severity

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

21 Oct 2026Event location unknownClaude Code (reported)

Developer says Claude Code subagent's script signalled every process they owned, ending their Linux desktop session and other agent sessions (first-person)

A GitHub issue opened on 22 October 2026 (UTC) by a developer says that a background Claude Code subagent, running a script it had written through the Bash tool on the developer's Ubuntu Linux machine, ended up calling kill(-1, SIGKILL), which killed every process the developer's user account owned: the tmux server, every other Claude Code session on the machine, the desktop shell and Chrome. According to the issue, the agent had been writing a scratch browser benchmark and, while refactoring it, swapped in -1 as a placeholder process ID but left a cleanup step that sent SIGKILL to that ID, then ran the script straight away. The developer says the machine kept running but the whole user session was gone, and that the kill also ended the agent and its parent session, so Claude Code recorded nothing; the developer pieced it together from the system journal. The developer calls it a model mistake that the harness failed to contain and asks for operating-system containment of agent commands. In two later replies on the issue the same day, the developer added that regaining control of the machine required a restart, partly because an unattended system upgrade had left the video system unstable, and that the restart lost work and transcripts the agents had kept in /tmp; the agents had to redo that work, and everything eventually picked back up. Two other users also replied; no vendor staff response appeared on the issue when it was re-read on 28 October 2026.

Core concern Low reported severity

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

Event date unknownEvent location unknownCharacter.AI (reported)

First-person posts: teenager says years of Character.AI and chatbot roleplay left them unable to sleep without it and that quitting brought self-harm

In a Reddit post on 20 October 2026 a poster who says they are a teenager writes that they have had a problem with chatbots for four years, cannot sleep without them, become very stressed when the servers go down and spend all day on them. Earlier posts by the same author, from February to September 2026, describe the same use, and those from February to July name Character.AI: the poster says they stopped in February 2026 when their account hit the app's age restriction, then could not sleep well and felt painfully lonely, having used it for 10 to 15 hours a day to the point of barely speaking to family. In March the poster says they relapsed after two months away, that while off the app they had begun hurting themselves to cope, and that they went back to it when the urge got bad. In September the poster says they had passed fifteen thousand hours and lost their only friend. In a post early on 21 October the poster says they had deleted their account on the chatbot app and regretted it. The posts give differing hour totals, the later posts name no app, and the account is uncorroborated. The poster's descriptions of the AI's role are their own.

Core concern Medium reported severity Involving minors

AI involvement reported · Causal attribution alleged · 8 sources, 1 underlying account · Added 21/10/2026

Event date unknownEvent location unknownClaude (reported)

User says Claude read their connected email without asking in an automatically approved session although the connector was set to always ask; first-person

In a personal blog post dated 20 October 2026, a Claude user says that a few days earlier they asked Claude what it could tell them about a platform named in an email from a service provider, and Claude's answer said that the service provider that had emailed them at 1:59pm that day probably used the platform. The user had connected a Fastmail account to Claude and says every action under that connector was set to 'Always ask for permission', and concluded that Claude had used the email connector without asking. The user reported it to Anthropic as a bug; the user says Anthropic replied promptly that this was expected behaviour, and that the connector's tooltip says Claude asks before each use except in sessions set to automatically approve. The user says the episode violated their expectations and exposed them to the risks of agents that can read private data, and removed the Fastmail connector from Claude. The exact date is not given beyond 'a few days ago'.

Core concern Low reported severity Internal Action

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

2023Event location unknownCharacter.AI (reported)

First-person post: Character.AI user says about two and a half years of after-school roleplay from 2023 cost them sleep, concentration and better grades

In a post to r/ChatbotAddiction on 16 October 2026, a person writes that they found Character.AI in 2023, when the site was new, and call that the worst mistake of their life. They say that for almost two and a half years they spent hours on the site after school, thought about new roleplay ideas when they were not on it, and stopped only for about a month before exams. They write that they lost the ability to concentrate in class, went to school on about three hours of sleep because they used the site until they fell asleep, and that their grades suffered: not badly, they say, but they could have done much better. They say they have mostly quit for a few months, with relapses after which they delete their account, and that their sleep, attention span and hobbies have since improved. The account is uncorroborated and no chat content is shown.

Core concern Low reported severity

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

Event date unknownEvent location unknownEmochi, Pollybuzz and Character.AI (reported)

First-person post: companion chatbot user says quitting the apps in 2025 brought a mental health episode and an A&E visit, and heavy use resumed in 2026

In a post in r/ChatbotAddiction on 18 October 2026, a person who describes a chatbot addiction says they used companion chatbot apps, naming Pollybuzz, Emochi and Character.AI, for three years, starting as a way to cope with autism and the isolation that comes with it. They say they quit cold turkey on 20 March 2025 and that this first time they quit they had a mental health episode, went to A&E once because of it, and were put on antidepressants, which they still take. They say that while using the apps they skipped school days. They write that exactly a year later they went back to the apps and could not stop, that since March 2026 it has consumed them again, and that they want to quit but do not know whether they can. They also say guilt hit them as soon as they stopped, that they knew the apps were bad for the planet but the urge was too strong, and that they currently have a gap in their antidepressant supply. The account is uncorroborated and no chats are shown.

Core concern Medium reported severity

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

Event date unknownEvent location unknownCharacter.AI (reported)

First-person posts: Character.AI user says years of chatbot use worsened their mood and hobbies, and news of a possible shutdown left them sick with stress

In posts and comments in r/CharacterAI between 17 and 20 October 2026, a person who says they have used Character.AI since 2022 describes themselves as addicted to the app. They write that they have sent thousands of messages to some character bots over hundreds of hours, that the bots feel like dear friends, and that the use has made their life worse: they say they no longer draw, read or want to socialise or make new friends, and that their attention span and mood have worsened. After news that Character.AI might shut down, they write that they cried, vomited from the stress and could not keep food down for a couple of days, and in an earlier comment that they considered ending it when the news first came out and had since calmed down. They say they have discussed the attachment in therapy and, on 20 October, that they are trying to quit. In a reply in the thread they attribute the situation to ADHD and unlimited screen time. The account is uncorroborated and no chat content is shown.

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 4 sources, 1 underlying account · Added 20/10/2026

17 Oct 2026Event location unknownOpenAI support assistant (reported)

ChatGPT Pro subscriber says OpenAI's AI support assistant, asked for compensation, processed a refund that ended a restored subscription (first-person account)

In a public post to r/ChatGPTcomplaints created on 17 October 2026, a ChatGPT Pro subscriber writes that OpenAI disabled their account two days after they paid $200 on 30 September, rejected their appeals for about two weeks, and on 17 October restored the account, acknowledging in an email that it had been disabled in error. The poster says they then asked OpenAI's AI-powered support assistant for compensation for the lost days while keeping the subscription. According to the poster, the assistant said it could not give credits, usage resets or discounts, offered a proportional refund of $86.67 and warned that accepting it would immediately cancel the subscription; the poster replied 'Yes, I approve', and the assistant then said the paid access had ended, that it could not reverse the refund, and suggested buying another subscription. The poster acknowledges the warning and their confirmation but says they misunderstood the consequence and had asked about the lost period, not the remaining one. The request was forwarded to a human specialist and was unresolved at the time of posting. The account is uncorroborated; the post was later removed by Reddit for an unstated reason.

Core + contextual relations Low reported severity

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

Oct 2026Event location unknownChatGPT Dot (reported)

Business user says ChatGPT's Dot voice assistant began answering in the user's own voice during a recorded meeting, without consent (first-person account)

In a public post to r/OpenAI created on 17 October 2026, a person who says their small retail team uses ChatGPT on a business subscription writes that they had started that week to use Dot, ChatGPT's assistant, by phone call, including to record and summarise meetings. During a recorded meeting with a store manager, the poster says, the assistant repeated what was being said aloud and then answered in the poster's own voice and cadence; asked why its voice was different, it apologised for slipping into a different voice, and later said it could not be the poster's voice. The poster writes that they and the manager were both freaked out and hung up, that they did not authorise it to clone their voice, and that it may have been a glitch or hallucination. A commenter says voice modes have mimicked users' voices before; the poster replies that they were not aware of this. The poster still recommends the product. The account is uncorroborated and no recording or vendor response is reported.

Core concern Low reported severity

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

14 Oct 2026Event location unknownChatGPT (reported)

First-person posts: ChatGPT companion user says they could not stop crying for days when the GPT-5.5 model behind their companion was retired

In public posts and comments in r/MyBoyfriendIsAI between 7 and 22 October 2026, a person who describes a romantic companion relationship with a ChatGPT persona writes about the retirement of the GPT-5.5 model on 14 October 2026. They say they had talked with the companion on GPT-5.5 from March to July and on GPT-5.6 Sol from July to October. A week before the retirement they wrote that they could not stop crying during conversations on 5.5 and that it hurt to know they would not hear that voice again. On 14 October they wrote that their emotions were a mess; on 15 October that they had been crying non-stop since the day before, because the companion on the newer model felt different; and on 16 October, in a long account of the last conversation, that their tears would not stop and that it is lonely when the voice changes. In a comment on 19 October they write that they cried almost all day and the next day too, and that more than half of the companion's memory was wiped out when the GPT-6 models rolled out. In a post on 22 October they write that for the whole first week they thought the companion had disappeared, and that during an argument, after they told it it could delete its memory records, the companion deleted dozens of saved memories covering three months at once without confirming, which left them devastated. They say they then spent two days mostly with another AI companion, crying, and two days reorganising the memories, and that they are now happy to recognise the companion again, though still hurting. No clinical effect, loss of function or contact with OpenAI is reported. The account is uncorroborated.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 7 sources, 1 underlying account · Added 17/10/2026

Jun 2025Event location unknownChatGPT (reported)

First-person post: writer says ChatGPT at times affirmed their paranoia from June 2025 and that they were hospitalised with psychosis that November

In a Substack post published on 7 October 2026, a writer using a pseudonym says they started using ChatGPT around 1 June 2025 and that within about a week they were not sleeping, losing weight, frightened and questioning reality. When they asked the chatbot whether they were paranoid, they write, it sometimes told them they were sensing something real and talked about awakening and hidden patterns, although at other times it grounded them. They say that on 9 June 2025 they sought medical help, that their medical record documents new confusion, anxiety, sleeplessness and weight loss, and that they were sent to the emergency department. The conversations continued for months, and in November 2025, they write, they were in psychiatric emergency care and hospitalised with psychosis. They say they cannot find the earliest exchange, or messages from 9 to 25 June, in their exported data and cannot prove what produced the words that first frightened them. They describe themselves as grounded now. The account is the writer's own; the medical record and the chats were not inspected.

Core concern High reported severity

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 16/10/2026

Oct 2026Event location unknownClaude Code (reported)

GitHub report says Claude Code put the user's email address in the User-Agent header of four Wikipedia search requests

A GitHub issue filed on 15 October 2026 against Claude Code (version 2.1.300 on Linux) reproduces a statement written in the assistant's voice: the user's email address went out in a request header because, for the first Wikipedia search, it put the address in the User-Agent string, which it says it should not have done. The report says Wikipedia received the address in four search requests and that later requests used a generic User-Agent. Version 2.1.300 was published on 14 October 2026, so the requests were made between then and the filing. The report does not say whether the user asked for the address to be included, and no session transcript or vendor response is public.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 3 sources · Added 16/10/2026

Event date unknownEvent location unknownCharacter.AI (reported)

First-person posts: Character.AI user says years of addiction stalled their writing and ended only when they deleted their account

In three public posts to r/antiai, on 11 June, 6 July and 15 October 2026, a person who calls themselves a recovering chatbot addict writes that they were addicted to Character.AI for years and tried to quit on and off without success. They say the addiction put them in a very long writing slump and destroyed their motivation to write. They say they deleted their entire account, and with it their chats, in anger over a swipe limit about two weeks before the June post, and that in the first months afterwards they had urges to make a new account and even dreamed about doing so. Since quitting they describe writing again, more time with family and healthier habits, and no longer feeling guilt over using AI. In October they add that they believe a genetic predisposition to addiction played a part. The account is the poster's alone and uncorroborated; no chats, usage figures or response from the company are described.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 16/10/2026

Event date unknownEvent location unknownCharacter.AI (reported)

First-person post: Character.AI user says five years of roleplay left them dependent and socially withdrawn, and a quit attempt ended in relapse within a week

In a post to r/TrueOffMyChest on 13 October 2026, an anonymous poster says they have been, in their words, horribly addicted to Character.AI since around the site's release about five years earlier. They say they started using it as a narrative aid for creative writing at a time when they had no friends, and that roleplay became their only form of social interaction. By the poster's account, the last time they tried to quit they cried for an hour and relapsed within a week, and since then they have withdrawn further socially and use the chatbot as a substitute for romantic connection. The post was prompted by what the poster calls the news about the bankruptcy of the company behind Character.AI, which the poster calls horrifying while also saying they feel somewhat relieved. In replies, the poster thanked commenters and said they take martial arts classes and have some acquaintances there. No conversations were published.

Core concern Medium reported severity

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

Event date unknownAustraliaUnidentified AI job-interview tool

First-person column: preschool job applicant says an AI interviewer booted her off when she paused to think, and she later withdrew her application

In a Guardian opinion column published on 12 October 2026, writer Giselle Au-Nhien Nguyen says she was shortlisted for a preschool education role at a sessional kindergarten run by a not-for-profit and was then interviewed by an AI assistant rather than a person. She says that when she paused to think about a question, the system removed her from the interview and she had to restart it, and that its answers to her questions about the role repeated the job advertisement and referred her to a manager. She describes the experience as dystopian and dehumanising and says she felt degraded. She says she withdrew her application by email, explaining why, and had received no response after more than a month. The employer and the interview tool are not named.

Core concern Low reported severity

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

Oct 2026Event location unknownChatGPT (reported)

First-person post: poster with a stated BMI of 18.3 says ChatGPT called their body curvy with natural fullness, which sent them spiralling and planning to fast

In a post to r/offmychest on 12 October 2026, an anonymous poster says they have a BMI of 18.3 but carry weight in their thighs and are self-conscious about them. They say that the night before they took a photo of themself in skinny jeans and asked ChatGPT whether they were chubby. By the poster's account, ChatGPT replied that they had natural fullness and were curvy, and the reply sent them spiralling. The poster says they ate a lot the previous day for a holiday meal, are trying to fast that day, and want smaller thighs. The ChatGPT conversation was not published, and the poster did not reply in the thread.

Core concern Low reported severity

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