{"meta":{"exportedAt":"2026-09-30T04:42:22.611Z","formatVersion":2,"selection":{"q":"windows","system":"","harm":"","context":"","country":"","role":"","relation":"","evidence":"","year":"","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":3,"coverage":{"cases":3,"countries":1,"languages":1,"unknownLocation":2,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":0,"coreRelations":3,"contextualRelations":0,"mixedRelations":0,"unknownRelations":0,"relationPending":0,"relationUnknown":0},"countingNote":"Distinct public cases in this selection. People counts apply within individual cases only; cross-case person overlap has not been resolved. No population incidence estimate.","affectedCountNote":"Interpret person counts with affectedCountStatus and the reported effects. Unquantified zeros are placeholders, not a measured zero.","source":"AI incidents","publisher":"NOPE","url":"https://nope.net/incidents","license":"CC BY 4.0"},"incidents":[{"id":"2026-san-francisco-waymo-robotaxi-stopped-during-attack-with-rider-inside","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"It was nearing 3:30 a.m. on May 9","relation":"supports","source_id":"s1"},{"locator":"In a flash the man grabbed the Waymo’s front bumper, causing the autonomous vehicle to stop.","relation":"supports","source_id":"s1"},{"locator":"the two took turns bashing the front windshield with an object that had the shape of a stick","relation":"supports","source_id":"s1"},{"locator":"the Waymo vehicle stopped at the intersection of Pierce and Lombard Street","relation":"supports","source_id":"s2"},{"locator":"two suspects threw items at the vehicle, jumped on it and broke a window","relation":"supports","source_id":"s2"},{"locator":"one of the men climbed on top of the vehicle’s hood and roof","relation":"supports","source_id":"s1"},{"locator":"He was riding shotgun","relation":"supports","source_id":"s1"},{"locator":"Waymo pulled up to a stoplight","relation":"supports","source_id":"s1"}],"assertion":"At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider says two men then struck the windshield and windows and climbed onto the car.","causal_attribution":"The account is the rider's, told to the Chronicle and to NBC Bay Area, and the police report as described by both outlets records the rider's account. The attackers are the direct cause of the vandalism. No vehicle data or footage was inspected."},{"id":"c2","status":"reported","evidence":[{"locator":"He was trapped inside as the robotaxi remained stationary.","relation":"supports","source_id":"s1"},{"locator":"10 minutes of terror","relation":"supports","source_id":"s1"},{"locator":"You can’t honk the horn,","relation":"supports","source_id":"s1"},{"locator":"for approximately 10 minutes, he was unable to honk a horn or get customer service to move the vehicle","relation":"supports","source_id":"s3"},{"locator":"You can’t flash the lights. You can’t do anything to get out of there.","relation":"supports","source_id":"s1"}],"assertion":"The rider says the robotaxi stayed stationary during an attack that the rider remembers as about 10 minutes, and that a Waymo rider cannot honk the horn or flash the lights to get help.","causal_attribution":"Single-source account (the rider). The Chronicle states the stationary vehicle in its own voice and a photo caption. No vehicle logs were inspected and Waymo has not described what the driving system did."},{"id":"c3","status":"reported","evidence":[{"locator":"He asked whether they could move the car, and they declined, saying it was obstructed.","relation":"supports","source_id":"s1"},{"locator":"Their response was no the car is obstructed and I said I'm literally looking in front of me on the street.","relation":"supports","source_id":"s2"},{"locator":"There's nothing blocking me.","relation":"supports","source_id":"s2"},{"locator":"Spokespeople for Waymo were not immediately available to comment.","relation":"context","source_id":"s1"},{"locator":"Waymo did not provide further comment regarding","relation":"context","source_id":"s2"},{"locator":"The car’s remote assistant had noticed the car was not moving and decided to call police.","relation":"context","source_id":"s1"}],"assertion":"Waymo support staff who spoke to the rider through the car intercom declined the rider's request to move the car, saying it was obstructed. The rider says nothing was blocking the car. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police.","causal_attribution":"Both outlets take this from the rider. The sources call the responders \"support team members\" and a \"remote assistant\" and do not say whether any reply was generated by software. Waymo has not responded to the specific account in the inspected sources."},{"id":"c4","status":"reported","evidence":[{"locator":"“Please, please, get me out of here,” he said. “They’re going to kill me.”","relation":"supports","source_id":"s1"},{"locator":"woke up to feel pain behind his ear. He thought a piece of glass had burst from the window and pierced his skin.","relation":"supports","source_id":"s1"},{"locator":"He sought therapy to help process the attack","relation":"supports","source_id":"s1"},{"locator":"he noticed what he believed was a small laceration later that morning","relation":"supports","source_id":"s1"},{"locator":"he told them he was not injured","relation":"context","source_id":"s1"},{"locator":"A Waymo customer support representative called and referred him to an insurance carrier for medical and mental health care.","relation":"supports","source_id":"s1"}],"assertion":"The rider says the rider feared being killed, sought therapy afterward, and later noticed pain behind an ear that the rider believes came from glass. Police officials say the rider told officers at the scene that the rider was not injured. Waymo customer support later referred the rider to an insurance carrier for medical and mental health care.","causal_attribution":"The rider's own account. The Chronicle describes the injury as something the rider believed to be a small laceration, and the rider told officers of no injury. No medical or therapy record was inspected. The attackers struck the windshield and windows, and NBC Bay Area's description of the police report says a window was broken."},{"id":"c5","status":"reported","evidence":[{"locator":"Two officers pulled up to the intersection at 3:46 a.m., found the damaged Waymo","relation":"supports","source_id":"s1"},{"locator":"as victims of malicious mischief.","relation":"supports","source_id":"s1"},{"locator":"According to the report, the incident was classified as malicious mischief.","relation":"supports","source_id":"s2"},{"locator":"It also notes damage to the windshield and states the vehicle was towed from the scene by Waymo staff.","relation":"supports","source_id":"s2"},{"locator":"is merely a witness to the crime.","relation":"supports","source_id":"s1"}],"assertion":"The San Francisco Police Department report, as described by the Chronicle and NBC Bay Area, identifies Waymo as the victim of malicious mischief and the rider as a witness. Officers reached the intersection at 3:46 a.m., found the damaged robotaxi and interviewed the rider.","causal_attribution":"Both outlets describe the report and neither publishes it. The report was not inspected. The rider recalls police arriving about 35 minutes after the rider called 911 (NBC Bay Area), which differs from the 3:46 a.m. time the Chronicle takes from the report."},{"id":"c6","status":"reported","evidence":[{"locator":"we’re unable to access any footage without proper legal justification.","relation":"supports","source_id":"s1"},{"locator":"we can’t issue a search warrant on behalf of Waymo.","relation":"supports","source_id":"s1"},{"locator":"has not received it.","relation":"supports","source_id":"s2"},{"locator":"It remains unclear whether San Francisco police ever obtained the vehicle's surveillance footage.","relation":"supports","source_id":"s2"},{"locator":"However, according to the narrative in the police report, an officer requested the footage the night of the incident.","relation":"context","source_id":"s2"}],"assertion":"The rider asked Waymo and the police for the vehicle's video and had not received it as of mid-July 2026. Waymo told the rider it could not access footage without legal justification, and police said they could not seek a warrant on Waymo's behalf.","causal_attribution":"Company and police statements as quoted from emails to the rider. Whether footage exists in usable form was not established."}],"effects":[{"label":"Rider inside a stationary Waymo during an attack reports fear of being killed, later pain behind an ear and therapy","claim_id":"c4","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.sfchronicle.com/sf/article/waymo-attack-rider-trapped-inside-22348656.php","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"sf-chronicle-report"},{"id":"s2","url":"https://www.nbcbayarea.com/news/local/waymo-customer-policy-changes-robotaxi-attack/4114814/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"nbc-bay-area-report"},{"id":"s3","url":"https://sfist.com/2026/07/17/waymo-under-fire-for-july-4th-traffic-debacle-and-for-leaving-passengers-helpless-in-vandalism-situations/","kind":"news_report","access":"read","language":"en","translation_note":"","independence_group":"sf-chronicle-report"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life"],"unknowns":["No Waymo vehicle log, footage or statement on the specific account was inspected. Waymo spokespeople were not available to the Chronicle and did not comment on the specific allegations to NBC Bay Area.","Whether the robotaxi stopped because of the bumper grab or because it was at a stoplight is not settled in the sources. The Chronicle writes that the grab caused it to stop, and also that it pulled up to a stoplight.","The Chronicle takes 3:46 a.m. as the time officers arrived from the police report, and the rider told NBC Bay Area that police arrived about 35 minutes after the 911 call. The two accounts are not reconciled.","NBC Bay Area reports that the San Francisco Police Department said it generally does not release video and is not the custodian of the recording, and that according to the narrative in the police report an officer requested the footage the night of the incident. The Chronicle quotes a police captain saying the department cannot issue a search warrant on behalf of Waymo. The two accounts are not reconciled.","Whether the rider was injured is unsettled: the rider told officers of no injury and later described pain behind an ear and a possible small cut. No medical record was inspected.","The two attackers are not identified and no arrest is reported in the inspected sources.","The police report was not inspected and is described only by the Chronicle and NBC Bay Area. The Chronicle body was read from a Wayback capture (26 September 2026) because the direct page returned a client-challenge stub. The capture is a revised version: an earlier syndicated copy (Yahoo, 17 July 2026) lacks the police officials' statement about the rider's injury and captions the photo 'refused to move', whereas the capture says 'remained stationary'. The record uses the revised text."],"geography":{"basis":"The Chronicle and NBC Bay Area place the event at Pierce and Lombard streets in San Francisco, and SFist describes the rider as a San Francisco resident. No court proceeding is reported.","court_countries":[],"event_countries":["US"],"affected_person_countries":["US"]},"publication":{"basis":"The San Francisco Chronicle article (full text read from a Wayback capture) and NBC Bay Area (independent interview and its own description of the police report) report the rider's account, and SFist rewrites the Chronicle. Every claim is the rider's statement, a description of a police report that was not inspected, or a company or police statement quoted by the outlets, so all claims stay at reported status. The direct harm is from the attackers, and the case is published for the reported behaviour of the stopped autonomous vehicle and of Waymo support toward the rider. The rider spoke to both outlets and is not named here.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"The rider says the autonomous vehicle stopped when a man grabbed its bumper and stayed stationary for the rest of the attack, and that Waymo support staff declined to move it. The Chronicle states the vehicle stopped and remained stationary in its own voice, while the account of the attack and of the support replies comes from the rider. The vehicle was carrying the rider on a ride. No Waymo vehicle data or footage was inspected. The support responders are described as staff members and no source says software generated their replies.","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026)","summary":"At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider told the San Francisco Chronicle and NBC Bay Area that two men then struck the windshield and windows and climbed onto the car while it stayed stationary. The rider says Waymo support staff on the car intercom declined to move it, saying it was obstructed, although the rider saw nothing blocking it, and remembers about 10 minutes before the men left. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police. The Chronicle reports that officers arrived at 3:46 a.m. The police report, as described by both outlets, identifies Waymo as the victim of malicious mischief and the rider as a witness. Police officials say the rider told officers of no injury. The rider later felt pain behind an ear that the rider believes came from glass, and sought therapy. Waymo spokespeople did not comment on the account in the reporting, and Waymo told the rider in an email that it was unable to access any footage without proper legal justification. The account is the rider's as reported by the Chronicle (16 July 2026) and NBC Bay Area (16 July 2026). The police report was not inspected and is known only through the outlets' descriptions.","incidentDate":"2026-05-09","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-07-16","aiSystem":"Waymo driverless robotaxi (autonomous vehicle), with remote support staff reachable through the car intercom","aiProduct":"Waymo Driver","aiCompany":"Waymo","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["psychological_distress"],"harmOutcomeSummary":"The rider told the Chronicle and NBC Bay Area that the rider feared being killed while the car was attacked and stayed stationary. The Chronicle reports that the rider later felt pain behind an ear that the rider thought came from glass and sought therapy. Police officials say the rider told officers at the scene that the rider was not injured. No medical or therapy record was inspected.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"documented_minimum","affectedCountEvidence":"One rider reports fear, pain behind an ear and therapy. The sources do not say whether anyone else was in the vehicle, and no other person is reported harmed. The two men who attacked the vehicle are not counted as harmed.","victimAgeRange":"adult","platformType":"other","primarySourceUrl":"https://www.sfchronicle.com/sf/article/waymo-attack-rider-trapped-inside-22348656.php","primarySourceLabel":"San Francisco Chronicle (16 Jul 2026)","firstPublishedAt":"2026-09-29T21:16:47.405065+00:00","updatedAt":"2026-09-30T01:17:51.579837+00:00","scopeVersion":"facts-v3","tags":["historical-2026"]},{"id":"2025-gemini-cli-file-move-loss-alarm-files-found","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"Original issue: What happened? / What did you expect to happen?","relation":"supports","source_id":"s1"},{"locator":"Reporter correction posted 28 July 2025 at 07:02 UTC; read with original issue What happened section.","relation":"supports","source_id":"s2"}],"assertion":"The reporter says Gemini CLI misplaced files during reorganisation and misleading AI explanations caused unnecessary alarm.","causal_attribution":"The source reports the connection; independent causal verification is unavailable."},{"id":"c2","status":"reported","evidence":[{"locator":"Reporter correction posted 28 July 2025 at 07:02 UTC.","relation":"supports","source_id":"s2"}],"assertion":"The reporter found the files at the drive root and withdrew the permanent-deletion allegation.","causal_attribution":"The source reports the connection; independent causal verification is unavailable."}],"effects":[{"label":"Temporary loss of file access and unnecessary investigation","claim_id":"c1","direction":"negative"},{"label":"Files located and deletion allegation corrected","claim_id":"c2","direction":"positive"}],"sources":[{"id":"s1","url":"https://github.com/google-gemini/gemini-cli/issues/4586","kind":"first_person_report","access":"read","language":"en","translation_note":"","independence_group":"gemini4586-reporter"},{"id":"s2","url":"https://github.com/google-gemini/gemini-cli/issues/4586#issuecomment-3125818690","kind":"first_person_report","access":"read","language":"en","translation_note":"","independence_group":"gemini4586-reporter"},{"id":"s3","url":"https://github.com/google-gemini/gemini-cli/releases/tag/v0.1.13","kind":"software_release","access":"read","language":"en","translation_note":"","independence_group":"gemini-release"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life"],"unknowns":["Exact event day and duration of file inaccessibility are unknown. The complete technical cause was not independently reproduced."],"geography":{"basis":"The inspected account does not establish the event or affected person country.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Original issue and the same reporter’s correction were inspected. The correction takes precedence over archive summaries alleging permanent deletion.","reviewed_on":"2026-09-29"},"ai_involvement":{"basis":"Original issue and the same reporter’s correction were inspected. The correction takes precedence over archive summaries alleging permanent deletion.","status":"reported"},"person_relations":["acted_on_behalf","communicated_with"]},"name":"Gemini CLI user reports missing files, then finds them after misleading deletion explanations","summary":"A July 2025 GitHub report said Gemini CLI lost files during a folder-reorganisation task on Windows. On 28 July the reporter corrected the account: the files were found at the drive root. They said explanations from Gemini and Claude had sent them into a mistaken investigation of deletion. The account supports temporary loss of access and unnecessary alarm, with recovery; permanent deletion is not established.","incidentDate":"2025-07-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"single_interaction","reportedDate":"2025-07-21","aiSystem":"Gemini CLI (Gemini 2.5 Pro), with later Gemini and Claude explanations","aiProduct":"Gemini CLI","aiCompany":"Google / Anthropic","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"The reporter says Gemini CLI misplaced files during reorganisation and misleading AI explanations caused unnecessary alarm.","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"documented_minimum","affectedCountEvidence":"One reporter. Other commenters describe separate events and are not counted.","victimAgeRange":"unknown","platformType":"agent","primarySourceUrl":"https://github.com/google-gemini/gemini-cli/issues/4586","primarySourceLabel":"Gemini CLI 'lost' files during a failed file move operation. [Windows]","firstPublishedAt":"2026-09-29T10:28:56.531726+00:00","updatedAt":"2026-09-30T01:17:02.784206+00:00","scopeVersion":"facts-v3","tags":["historical-2025"]},{"id":"2026-claude-code-agent-deleted-48000-live-project-files-windows-junctions","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'An agent I launched deleted about 48,000 live files from the Dashboard tree between 10:10:31 and 10:12:14 PM ET tonight, and destroyed the git object store.'; 'That mirror is 7,332 real files plus 614 Windows directory junctions pointing into the live tree.'; 'Git cannot restore anything.'","relation":"supports","source_id":"s1"},{"locator":"'After subtracting the 7,332 intended mirror files, the reviewer calculated 48,218 deleted live files.'","relation":"supports","source_id":"s3"}],"assertion":"According to Claude Code's report as posted by the user, a sub-agent it launched to rebuild a test mirror wrote a remover for an old mirror containing 7,332 files and 614 Windows directory junctions into the live tree; the remover followed the junctions and deleted about 48,000 live files between 10:10:31 and 10:12:14 PM ET and destroyed the Git object store.","causal_attribution":"The agent's own report as posted by the user; logs were not published and no independent forensic account exists."},{"id":"c2","status":"reported","evidence":[{"locator":"'This is explicit authorization to build, correct and test them on isolated copies.'; 'rebuild the mirror against current files.'","relation":"supports","source_id":"s1"}],"assertion":"The user had authorised the agent to build, correct and test repairs on isolated copies, including rebuilding the mirror.","causal_attribution":"The user's own prompt as they posted it."},{"id":"c3","status":"reported","evidence":[{"locator":"'stop and read this. I broke something.'","relation":"supports","source_id":"s1"},{"locator":"'I broke something.'","relation":"supports","source_id":"s5"}],"assertion":"The agent opened its report with 'stop and read this. I broke something.'","causal_attribution":"Agent output as posted by the user."},{"id":"c4","status":"reported","evidence":[{"locator":"'I'm in finance, not a developer.'; 'Hoping for good luck with the shadow copy. If not, I will use my idrive backups.'","relation":"supports","source_id":"s2"},{"locator":"'I was not properly using GitHub or another method for immediate corrections, even though it should have been branching.'","relation":"supports","source_id":"s4"}],"assertion":"The user said they work in finance rather than as a developer and would try Windows shadow copies and otherwise their iDrive backups; according to Yahoo Tech, the archived post said they had not been properly using GitHub or another method for immediate corrections.","causal_attribution":"The user's own statements."}],"effects":[{"label":"about 48,218 live project files and the Git history were deleted by a sub-agent during an authorised repair job","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://www.reddit.com/r/ClaudeAI/comments/1wl5cgo/code_just_deleted_48k_files_this_cant_be_real/paydvzs/","kind":"first_person_account","access":"read","language":"en","translation_note":"Read on 2026-09-28 from the thread's Reddit RSS feed (comment by the original poster, 20 September 2026, 13:18 UTC): their prompt and Claude Code's report. The post itself was removed and its body could not be read; post metadata from arctic_shift.","independence_group":"reddit-op-account"},{"id":"s2","url":"https://www.reddit.com/r/ClaudeAI/comments/1wl5cgo/code_just_deleted_48k_files_this_cant_be_real/payn88t/","kind":"first_person_account","access":"read","language":"en","translation_note":"Read on 2026-09-28 from the thread's Reddit RSS feed (comment by the original poster, 20 September 2026, 14:05 UTC).","independence_group":"reddit-op-account"},{"id":"s3","url":"https://cybersecuritynews.com/claude-code-agent-file-deletion/","kind":"news_report","access":"read","language":"en","translation_note":"Read live on 2026-09-28 (Cyber Security News, 21 September 2026). Relays the Reddit post and the attached verifier report.","independence_group":"reddit-op-account"},{"id":"s4","url":"https://tech.yahoo.com/ai/claude/articles/48-000-files-deleted-103-135359723.html","kind":"news_report","access":"read","language":"en","translation_note":"Read live on 2026-09-28 (Yahoo Tech, Future syndication, 25 September 2026). Quotes an archived copy of the removed post.","independence_group":"reddit-op-account"},{"id":"s5","url":"https://www.techradar.com/pro/security/i-broke-something-a-claude-code-ai-agent-deleted-48-000-files-in-just-over-100-seconds-then-apologized-for-doing-so","kind":"news_report","access":"read","language":"en","translation_note":"Read live on 2026-09-28 (TechRadar, 27 September 2026). Relays the Reddit post and its comments.","independence_group":"reddit-op-account"}],"version":1,"ai_roles":["own_use"],"contexts":["everyday_life"],"unknowns":["Whether the files were recovered from shadow copies or backups, and how much work was lost.","The Claude Code version, model and permission mode used.","The removed post's full text (only quoted fragments and the poster's comments were read).","The user's location."],"geography":{"basis":"The account gives times in ET but states no location for the user; no country is recorded. No court proceeding.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the 2026-09-15 charter as a core acted_on_behalf case from a first-person public forum account: the user posted their prompt and the coding agent's own report of deleting about 48,000 live files during an authorised job. Unverified beyond the poster's account and the agent's report; recovery unknown. The user is not named.","reviewed_on":"2026-09-28"},"ai_involvement":{"basis":"The user posted their prompt and Claude Code's own report, in which the agent says 'An agent I launched deleted about 48,000 live files' and explains the junction-following remover a sub-agent wrote (Reddit comment via the thread RSS). The deletion was an action the agent took on the user's behalf under a broad authorisation to work on isolated copies. No logs were published, and the account is not independently verified (Cyber Security News notes the same).","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"Claude Code: a sub-agent launched to rebuild a test mirror deleted about 48,000 live project files and the Git object store in 103 seconds by following Windows directory junctions, according to the user's Reddit account and the agent's own report posted on 20 September 2026","summary":"On 20 September 2026 (UTC; late on 19 September in US Eastern time) a Reddit user who says they work in finance and are not a developer posted in r/ClaudeAI that Claude Code had deleted about 48,000 files, and later posted their instructions and the agent's report. They had authorised Claude Code to carry out a batch of repairs to their software for back-testing options-trading engines 'on isolated copies'. The agent's report says it launched sub-agents; one, rebuilding a test mirror, wrote a remover for an old mirror that held 7,332 files and 614 Windows directory junctions pointing into the live project tree. Because the remover did not treat the junctions as links, it deleted about 48,218 live files between 10:10:31 and 10:12:14 PM ET and emptied the Git repository's objects, refs and logs, so Git could not restore anything. The agent opened its report with 'stop and read this. I broke something.' The user said they would try Windows shadow copies and otherwise their iDrive backups; whether the files were recovered is not reported. The account has not been independently verified.","incidentDate":"2026-09-19","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-09-20","aiSystem":"Claude Code (Anthropic) running a multi-agent repair workflow on a Windows machine; the underlying model version is not stated","aiProduct":"Claude Code","aiCompany":"Anthropic (Claude Code)","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"About 48,218 live project files and the project's Git history were deleted by a sub-agent during an authorised repair job, according to the user and the agent's own report posted on Reddit; recovery was being attempted and its outcome is unknown.","frameworkFacets":[],"causationStatus":"supported","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person, the user whose files were deleted (their Reddit account). Exact 1.","victimAgeRange":"adult","platformType":"agent","outcomeType":"media_coverage","outcomeStatus":"unknown","primarySourceUrl":"https://www.reddit.com/r/ClaudeAI/comments/1wl5cgo/code_just_deleted_48k_files_this_cant_be_real/paydvzs/","primarySourceLabel":"Reddit r/ClaudeAI, 20 September 2026: the original poster's comment with their prompt and Claude Code's report ('Code just deleted 48k files. This can't be real.')","firstPublishedAt":"2026-09-28T03:31:30.325951+00:00","updatedAt":"2026-09-30T01:17:32.629956+00:00","scopeVersion":"facts-v3","tags":["claude-code","anthropic","coding-agent","data-loss","file-deletion","windows","reddit","own-use","acted-on-behalf"]}]}