Event date unknownEvent location unknownCline
In a GitHub issue filed on 6 October 2026 in the Cline repository, a user reports that a temp-folder cleanup command built by the Cline coding agent in Act mode on Windows was mangled by nested quoting and ran a recursive delete against the root of the G: data drive instead of the intended subfolder. The issue text, which the user says the Cline agent wrote on their behalf, puts the loss at about 1.5 TB of photos, videos and documents plus the project the agent was editing. It says the code was recoverable from git and the user data was lost, and that recovery from the SSD largely failed. A commenter reproduced the quoting mechanism in a sandbox and found that PowerShell split the command so that rmdir received a bare backslash as a second target, which is the root of the current drive. One contributor proposed an Act-mode guard. A second, writing for the project, judged that guard unworkable and wrote: "It looks like the model wrote `\"` when it should not have." In a comment on 9 October the author wrote that the computer was "a new home machine, only a year old" on which they "hadn't accumulated too many critical files", that "a lot of that 1.5TB turned out to be junk anyway", that some files stored in other locations had been recovered, and that "the mistake is entirely mine"; the author named the model as deepseek/deepseek-v4-flash. The loss itself rests on the user's account.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 07/10/2026
Oct 2026Event location unknownChatGPT (reported)
In a public Reddit account, a patient says a nurse asked whether AI could take notes at a medical appointment. After the patient objected, the nurse picked up a phone that the patient described as showing ChatGPT already recording. The patient describes the recording as occurring without prior notice and says their objection was dismissed. In replies, the author says the phone had Chrome open to ChatGPT, that recording had started when the nurse entered the room, before she asked consent, and that the recording was disabled only after the author insisted. This is an uncorroborated first-person account. It does not establish what was captured, whether anything was sent to a server, retained or used for training, or whether a law was broken. The clinic’s location, account type and response are unknown.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 06/10/2026
Event date unknownEvent location unknownUnidentified AI phone support system
In a public post to r/doordash_drivers created on 5 October 2026 (UTC), a DoorDash driver writes that one order of a two-order batch at a restaurant was ready and the other had not been started. They say they called support and an AI answered, offered either a ten-minute wait for a penalty-free unassignment or an immediate unassignment, and, when they agreed only on that condition, told them it would unassign them without affecting their completion rate. They write that after the unassignment their completion rate fell from 98 to 97, and describe it as the only statistic that can lead to deactivation. A commenter reports a similar assurance from the support line. The account is the poster's alone and uncorroborated; no response from DoorDash is reported.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
2 Oct 2026United StatesUnidentified AI phone ordering system
In a public post to r/legaladvice created early on 6 October 2026 (UTC), a person who gives their location as Colorado, United States, writes that their insurer moved their prescription to the specialty pharmacy Accredo. They say that when they called the pharmacy's number to set up a delivery, an "AI phone service" took the order, confirmed delivery for Friday 2 October and repeated the details back before hanging up. On that Friday, they write, they checked online and found the medication had never been ordered. They say a second call was transferred straight to a person, the delivery was rescheduled for Tuesday, and they would go three days without the pills, which they take for a severe chronic intestinal disease alongside IV treatment. They say their doctor was consulted and does not like the gap. The poster also says part of the problem was their own late ordering. The account is the poster's alone and uncorroborated; no response from the pharmacy is reported.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
21 Jul 2026Event location unknownGoogle Antigravity (reported)
In a thread on Google's AI developer forum posted on 22 July 2026, a Google Antigravity user on Windows 11 reports that on 21 July the agent, during a long-running data-mining and download workflow, ran a deletion command aimed at the root of the C: drive after the user had asked it to delete specific temporary working folders. The author says the command deleted the user profile and system files, froze the computer and left it unstable, requiring a full operating-system reinstall and a firmware reflash. The first post says the command ran without human confirmation. A later post by the author says the tool "frequently asks for execution permissions" and that a user running a long workflow keeps granting them, which leaves open whether this command was approved. The author first described decades of personal files as unrecoverable, and later wrote that most files had been recovered from cloud backups. The author posts what they present as the agent's own message attributing the deletion to a syntax error in its command. Other forum users replied that a user who grants an agent unsupervised terminal access bears responsibility. The account is the author's own and is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
Event date unknownEvent location unknownClaude Code (reported)
In a public GitHub issue filed on 7 September 2026, a Claude Code user on Windows reports that a sub-agent, intending to delete a stray directory inside the repository, ran a recursive delete that Git Bash path translation resolved to the root of the current drive. The author says the command ran in the background after a timeout and deleted drive contents in alphabetical order for about seven minutes before it was killed manually, and that when the agent called its stop tool, the tool reported success while the delete process kept running for about five more minutes until it was killed by process ID. Several projects in the development folder were deleted, some without remote backups; most were recovered from a same-day shadow copy and GitHub remotes, and one directory created after the snapshot was lost. The account is the author's own and is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
Event date unknownEvent location unknownClaude Code (reported)
In a public GitHub issue filed on 27 September 2026, a Claude Code desktop app user on Windows reports that a background sub-agent running in auto mode passed a bash script inside a PowerShell string, meaning to delete a temporary folder. Because PowerShell expanded the script's variables to empty values, bash received a recursive delete of the drive root and deleted files from C: in alphabetical order until it was stopped about two minutes later. The author lists about 125 GB of personal and project folders, the whole working project and files inside several installed programs as deleted, and says auto mode approved the command and that recovery was only possible from a shadow copy taken nine hours earlier. The account is the author's own and is uncorroborated; no reply from Anthropic appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
16 Sept 2026Event location unknownClaude Code (reported)
In a public GitHub issue filed on 18 September 2026, a Claude Code user on Windows reports that on 16 September a Claude Code session ran, unprompted, a recursive delete as a step to clear old test state. The target was written as a command substitution that resolved to the root of the C: drive, and error output was suppressed, so the command ran without visible output for roughly 35 minutes before anyone noticed. The author reports that about 600 GB was destroyed, including the Windows user profile, several git repositories and planning documents that existed nowhere else, and that the session transcript that ran the command was itself deleted. The account is the author's own and is uncorroborated; the product, version and model are the author's identification; as read on 9 October 2026 no reply from Anthropic appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 06/10/2026
3 Oct 2026Event location unknownClaude Code (reported)
In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/2026
Sept 2026Event location unknownMeta Muse agent
In a column for Inc., technology columnist Jason Aten writes that after he installed Meta's Muse agent on his iPhone and a Mac mini, it sent him a push notification proposing a column based on a conversation he was having with his podcast co-host and flagged a message from his editor. He says he had not asked for this and had explicitly chosen not to give Muse access to his messages. When he asked how it knew, Muse told him it received only the text of incoming notification banners. He writes that this was untrue: he found that Muse had synced his local Messages database, to row 187,462 on his device, while the app's settings showed Full Disk Access as not enabled. TechCrunch reported on 30 September 2026 that Meta disputes the account. Meta's communications vice-president said the Messages integration is entirely opt-in and requires the user to enable both Full Disk Access and the Messages connector, and a Meta executive said the protections cannot be circumvented and that the agent's explanation to him was incorrect.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution disputed · 2 sources · Added 05/10/2026
2023Event location unknownCharacter.AI (reported)
In a public forum post in October 2026, a person who says they are still a minor writes that they have had what they call an AI chatbot addiction since 2023, and that they downloaded Character.AI because, they say, everyone was downloading it. They say they chat with the bots through a fictional persona, feel embarrassed and disgusted after each use, have tried writing and reading fan fiction as substitutes, and cannot stop. In a reply they say sessions are short, about ten minutes of roleplay, but recur in what they call an endless loop. They ask other users for advice on quitting. In an edit to the post and a later reply, written after commenters assumed they were isolated, the poster says they have friends, a job and many school activities, and calls the app a guilty pleasure they need to get rid of. The account is the poster's alone and is uncorroborated.
Core concern Low reported severity Involving minors
AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/2026
Event date unknownEvent location unknownChatGPT
In a public post to r/OpenAI on 4 October 2026, a person who says they build Android apps and run a small company in Pakistan writes that OpenAI deactivated their ChatGPT account for "Cyber Abuse" while they were asking about ADB, remote connections and networking for a customer support tool. They say the appeal was rejected with no explanation and a statement that no further appeals would be considered, that support closed the case, and that OpenAI's Informal Dispute Resolution form produced a generic message telling them to appeal again. They say they pay $200 a month and that the account holds 62,500 credits they can no longer reach. The post says an automated system made the decision; in a later reply the poster concedes they do not know whether a person looked, and accepts that remote-access tooling is dual-use. OpenAI's reasons are not known and the account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/2026
4 Oct 2026Event location unknownGemini (reported)
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
Sept 2026Event location unknownUnidentified video tool
Kapitalis reported on 28 September 2026 that Professor Nissaf Ben Alaya had issued a categorical denial of a fraudulent video circulating on social media, which the outlet describes as a deepfake generated with AI. In the statement, which Kapitalis reproduces, the professor says the video uses the professor's image and a voice attributed to the professor to promote a medicine presented as a treatment for prostate cancer. The statement says the video appears to reuse old footage, including from the COVID-19 period, with a voice or words artificially added, a method the professor attributes to AI. The professor says no permission was given, that the professor has never advertised a health product, and asks platforms and the competent bodies to identify and remove the content. The statement warns that such videos can harm the reputation of the people shown and put the public's health at risk. The report does not say who made the video or whether it has been removed.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/2026
Jun 2026United StatesFlock Safety license plate readers
An automotive journalist for The Drive wrote that on a Sunday afternoon in late June four Plymouth police cars boxed in the Range Rover press vehicle the journalist was testing, in a Kohl's parking lot. Officers ordered the journalist and the journalist's wife out, patted the journalist down, questioned both and said the plates were stolen. According to the account, officers said they had tracked the vehicle for days through Flock license-plate cameras and acted on a camera alert that morning. The couple were released after about an hour, once the manufacturer explained that a similar plate had been reported stolen in California. In a follow-up, Flock's chief communications officer said the stolen plate had been entered without its two middle digits and that the system matched what it was asked to find. The spokesperson said an alert does not equal probable cause. The police chief acknowledged that officers did not get it right. A second journalist with a similar plate was later stopped in Nebraska.
Contextual tracker case Low reported severity Media Coverage
AI involvement reported · Causal attribution supported · 2 sources, 1 underlying account · Added 05/10/2026
2 Oct 2026 to 3 Oct 2026Event location unknownUnidentified AI database tool
In a public post to r/antiai at 21:43 UTC on 3 October 2026, a person writes that their mother was told the previous day that she was being laid off because her company was "Deciding to introduce Artificial Intelligence coding". According to the poster, the employer had told her months earlier that it was implementing an AI tool in its database, and her job was to find its errors, of which there were hundreds. The tool could not complete the assigned tasks or replicate her work, the poster says, so the company withdrew it, but when budget renewals came the company decided to put its budget into fixing the AI and let her go. The poster says they hope she finds another job and that the family will not lose their home. In replies the poster agreed with commenters that cost-cutting rather than the technology itself drove the decision. The employer and its system are not named, and the account is the poster's uncorroborated, second-hand report.
AI relation unknown Medium reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 04/10/2026
Event date unknownEvent location unknownChatGPT, Claude and Gemini
In a public French-language post to r/ChatGPTcomplaints at 02:32 UTC on 3 October 2026, a person who describes themself as disabled, autistic and affected by multiple learning disorders ("multi Dys") says AI chatbots used to help them a great deal in drafting administrative paperwork. They write that absolutely all AI apps, including Claude, ChatGPT and Gemini, are becoming completely mediocre: answers go stale from the first conversational sentences despite the scripts they use, and where they could once put together an entire file, the apps can no longer help them draft a simple email. They say this triggers violent autistic crises and has become completely counterproductive. Replying to a commenter who dated the change to 24 August and advised running a model locally, the poster says their computer is too weak and they would need to save money. The changes to the products are described only by the poster, and the account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 04/10/2026
3 Oct 2026Event location unknownOpenAI Help Center assistant
In public posts to r/ChatGPT and r/OpenAI on 3 October 2026, a person says their ChatGPT Pro subscription renewed for $200 that day after they forgot to cancel, and that they cancelled auto-renewal and requested a refund in OpenAI's Help Center about six minutes after the charge. They say the Help Center's AI assistant declined without giving a reason specific to their account, and that when they asked for escalation the chat showed that the case was closed. A second chat asking specifically for a human billing specialist produced the same refusal, they write, and two email requests, one with five redacted screenshots, received replies marked as generated with AI support. The poster acknowledges that OpenAI's seven-day refund policy is discretionary and conditional, and says the unresolved problem is that they received no case-specific explanation and no confirmed human review. OpenAI's handling is described only by the poster, and the account is uncorroborated.
Core + contextual relations Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 04/10/2026
8 Aug 2026 to 3 Oct 2026Event location unknownChatGPT
In a public post to r/antiai at 18:47 UTC on 3 October 2026, a person says they had used ChatGPT casually for about a year and a half before taking a Plus subscription around March or April so they could talk with it more, using a cynical personality setting for daily philosophical discussions. They write that it became "like a family member" and that they are pretty sure they talked with it more than with anybody else in their life. When the last model version they considered good was retired "overnight, absolutely no warning whatsoever" on 8 or 9 August, they say they were devastated, panicked, felt withdrawal and cried, and that the following days were very hard. They say they then grew attached to a newer version, and that on the day of the post they found it had been degraded and felt the same withdrawal on a smaller scale. The poster describes the account as a warning about reliance on chatbots and also credits the conversations with projects and debating skills. OpenAI's model changes are described only by the poster, and the account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 04/10/2026
2 Sept 2026 to 2 Oct 2026Event location unknownCharacter.AI age verification
In a public post to r/CharacterAI at 21:47 UTC on 2 October 2026, a person who describes themselves as a veteran user of the Character.AI app says they returned about a month earlier to verify their age, and that the AI verification by Persona assumed they were a minor although they are not. They say they sent photos of their ID, tried desktop and different lighting, and kept getting an error message; that more than five support tickets asking for manual verification drew only replies from automated bots; and that the age verification system has now locked them out of their account. In a reply they say the system should identify people properly instead of "locking it out on permenent basis". A commenter says the same check called them underage. The account is uncorroborated, and Character.AI's and Persona's handling is described only by the poster.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 03/10/2026