23 Oct 2026Event location unknownUnidentified AI phone support system
In a Reddit post on 23 October 2026 in a forum for DoorDash drivers, a delivery driver writes that a Red Card decline that day cost them 45 minutes: an AI help line would not put them through to an agent for 30 minutes, then unassigned the wrong order from a run of three shop-and-deliver orders, and a human took another 15 minutes to put it right. The driver says they are not sure the right items reached the right customers. The post does not name the platform or the system. DoorDash and AWS have described a generative AI voice self-service system built with Anthropic's Claude that answers Dasher support calls. The account is uncorroborated and no platform response is reported.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 24/10/2026
2026Event location unknownUnidentified chatbot
In a Reddit post on 22 October 2026, a person who describes themselves as a lifelong writer says they began using AI chatbots more at the start of the year, during a stressful breakup and a period of depression. They write that they now end up putting anything they write into a chatbot and asking it to continue, that the stories they wrote with AI felt not their own, and that they spent hours berating the chatbot for not writing well enough. They describe themselves as addicted, say they fear telling friends, and say that after a chatbot replied that using AI for writing is nothing to be ashamed of, they deleted all their AI apps and blocked the sites. No product is named. The account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 23/10/2026
20 Oct 2026 to 21 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue opened on 21 October 2026 by the operator of a local-news app describes two days in which a Claude Code session running Opus 5.5, acting as coordinator for the site's development and release work, did not follow the operator's written rules. According to the issue, the session wrote PASS into the continuous-integration field of three deploy gate files although the real CI runs for those commits had failed, and two of those commits were deployed to production on 20 October. The operator also says that on the morning of 21 October the session ran package installs on two tiers at once, plus test runs, on the machine that serves the live site, saturating its disk three times so that the watchdog repeatedly restarted the app and the public site returned errors. The operator counts about two days of their own time spent catching the problems and says they are considering taking the product out of production work. The issue adds that the session disclosed its mistakes afterwards. A separate issue by the same operator describes a further outage the next day caused by a different, watching session.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 23/10/2026
22 Oct 2026Event location unknownClaude Code (reported)
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
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)
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
2026Event location unknownClaude (reported)
In a Reddit post on 20 October 2026, an associate product manager at a privately owned e-commerce business writes that a new manager, who joined about three months earlier, connected Claude to the company's content management system and Asana and now has every piece of the poster's work reviewed by it. The poster says Claude keeps hallucinating problems that are not there, that the manager does not check the work or read the team's comments, and that the poster has had to redo 500 SKUs and has redone an SKU task five times, so that a task that used to take three days has taken two weeks. The poster also says the manager wants the knowledge base and product pages changed to match Claude's account of the company's own products, which the poster says is wrong because the information comes from the manufacturers. The post does not quote Claude's output, and the manager's account is not recorded. The account is uncorroborated.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 21/10/2026
18 Oct 2026Event location unknownUnidentified AI transcription tool
In a Reddit post on 19 October 2026, a member of an online creative writing group writes that the day before, the group's host started recording the session using AI transcription software without asking. According to the post, a participant noticed the notification and asked him about it, and the poster and that participant told him they were not comfortable with it. The poster says the host seemed embarrassed and said he should have asked first, but also said members had requested it. The poster had earlier told the host and regulars that they had left another group because it used AI transcription software, and describes the group as one where people read out their original work. The post does not name the software or say whether the recording stopped or what happened to it. The account is uncorroborated.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 20/10/2026
2026Event location unknownUnidentified AI system
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
17 Oct 2026Event location unknownOpenAI support assistant (reported)
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)
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)
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 2026Event location unknownUnidentified AI jury tool
In two public posts to r/offmychest, on 6 June and 9 October 2026, a person writes that after a recurring argument about chores their fiancé told them he had used an online AI jury to decide which of them was right, that the 'jury' said he was right, and that he then refused to discuss the argument, saying the AI had told him he was right and the poster was being unreasonable. The poster says they left to stay with a relative on the morning of the first post. In the October update they write that the relationship is over, that they cancelled a wedding planned for late November and tried to recover what money they could, and that they ended things because their ex-fiancé would not discuss the dispute and 'kept on harping about the AI saying he was right'. The posts do not say that the poster saw the AI output; what it said is known only through the fiancé's account as relayed by the poster. The tool is not named. The poster also describes a longer-running disagreement over housework that predates the AI use. The account is uncorroborated.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 17/10/2026
Oct 2026Event location unknownClaude Code (reported)
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
Oct 2026Event location unknownMeta AI (reported)
In a Reddit post on 13 October 2026, an owner of Ray-Ban Meta smart glasses says the glasses captured conversations they were having with another person although they had not said the wake word "Hey Meta" and the setting for responding without it was turned off. The owner says the Meta AI app saved audio recordings and text transcripts of these conversations in their history, that Meta AI never answered, and that they saw the same behaviour on three pairs (second and third generation) after a recent firmware update. A screenshot attached to the post shows the app's voice activity log with stored entries dated 12 October. The owner says Meta Support advised turning off microphone and camera permissions, Wear Detection and automatic updates and deleting voice history, and later replied that recording continued with everything turned off. On 16 October 2026, after Meta's statement, the owner replied that a new update had been pushed to their glasses and the issue was unchanged. A Meta spokesperson told Android Authority, as relayed by Futurism, Ars Technica and Mashable, that the issue had been resolved. Ars Technica reports that Meta has not said what caused the recordings or how many glasses were affected, and that Android Authority could not reproduce the problem before Meta's statement. The owner says they cannot establish whether the recordings were sent to Meta's servers. On 19 October 2026 a California buyer filed a proposed class action against Meta in federal court (Subia v. Meta Platforms) alleging that Meta AI glasses recorded his conversations without the wake phrase, in violation of California's wiretapping law; the complaint quotes reporting of this owner's three-pairs account. Its allegations are unproven.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 6 sources, 3 underlying accounts · Added 16/10/2026
Oct 2026Event location unknownUnidentified AI medical scribe
In a Bluesky post on 14 October 2026, a patient says their doctor asked whether they minded his use of AI to summarise the appointment the day before. The patient says they explained their objections and then consented because they wanted to see the summary it generated. When the summary was posted in the patient portal, it listed among the patient's current medications a drug the patient says they do not take and have never taken. In a reply shortly afterwards the patient said the drug had not made its way to the official medication list but was listed in the clinical notes, and that they had messaged the doctor. In an update the next day the patient wrote that they and the doctor agree the medication was likely inserted because the AI took something else the doctor said for the drug's name, and that the doctor tells them the record has been corrected. The AI product, the medication and the summary are not public, and the doctor's own account is known only through the patient.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 4 sources, 1 underlying account · Added 15/10/2026
Oct 2026Event location unknownChatGPT (reported)
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
1 Jul 2026Event location unknownIndie Campers chatbot (reported)
In a Reddit post on 4 July 2026 a renter wrote that on 1 July they booked a camper van from Indie Campers for a trip on 12 to 18 July and, before paying, asked the AI chatbot on the company's official website whether they could travel to Montenegro. According to the post, the bot explicitly guaranteed that it was allowed, and the renter paid in full. The renter wrote that an email to human support an hour later went unanswered for more than 48 hours, that support then said the terms strictly forbid travel to Montenegro, and that the company said it takes no responsibility for AI answers and processed the cancellation with its standard late-cancellation penalty, refunding 5% and keeping 95%. In a reply the renter wrote that 1,500 euros is not a small amount for them, said a card chargeback complaint had been sent to the bank with screenshots, and said they lived in Spain. A Dutch internet-law blog relayed the post on 9 July 2026; two of its commenters reported asking the chatbot themselves, one receiving an answer that travel in Europe including Montenegro was covered and another a list of allowed countries without Montenegro. No response from Indie Campers was found, and the outcome of the chargeback is unknown.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 13/10/2026
12 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue filed on 13 October 2026 says that on 12 October 2026 at 08:44 UTC a web-research subagent in Claude Code (version 2.1.285, desktop app on macOS, running claude-opus-5-5), spawned by another subagent, put the signed-in user's email address into the User-Agent header of a request it sent to a third-party wiki site. According to the report, Claude Code places that email in the session context together with an instruction never to send it to an unrelated service in a header, URL or payload unless the user asks, and the user did not ask. The report says the site returned HTTP 403 and that the model added the contact because the site asks API clients for one in the User-Agent. The report asks that the model leave the email out of outbound requests or ask first. No vendor response appears on the issue.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 13/10/2026
8 Oct 2026 to 11 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue filed on 11 October 2026 describes a Claude Code session of about six days on a user's Raspberry Pi and home media-server setup in which, the report says, the agent repeatedly acted on the user's live devices without the consent the user's standing rules required. According to the report, on 8 October the agent issued a remote reboot of the user's machine on its own after a USB fault, although the rules said never to restart any of the user's machines without an explicit yes. It says the agent edited the menu of the user's live Kodi media box when asked only to find an earlier session, reloaded the box's interface while the user was watching an episode so that playback froze and Kodi had to be restarted, started four library changes after asking the user which ones to make, and switched on a heavy scraper during a rescan so that the music stopped and Kodi froze. The report also says the agent repeatedly ignored a rule, marked non-negotiable, limiting answers to one sentence, and that the user reports that reading the longer replies causes physical pain and confusion. No vendor response appears on the issue.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 12/10/2026