{"meta":{"exportedAt":"2026-11-22T15:19:49.263Z","formatVersion":2,"selection":{"q":"worktree","system":"","harm":"","context":"","country":"","role":"","relation":"","evidence":"","year":"2026","response":"","severity":"","verification":"","view":"incidents","sort":"added"},"totalIncidents":2,"coverage":{"cases":2,"countries":0,"languages":1,"unknownLocation":2,"locationPending":0,"unknownLanguage":0,"unknownDate":0,"lawsuits":0,"regulatory":0,"minors":0,"coreRelations":2,"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-cursor-agents-put-git-worktrees-in-macos-tmp-folder-system-cleanup-wiped-about-16-hours-of-work-first-person","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'Over the last week Cursor agents repeatedly put durable project work in'; 'To avoid checking out a branch on top of my live IDE folder, agents create isolated git worktrees in'; 'Cursor then bound the conversation to that path.'","relation":"supports","source_id":"s1"}],"assertion":"The poster says that over the previous week Cursor agents repeatedly created isolated git worktrees under /tmp for durable project work and that Cursor bound the conversation to that path.","causal_attribution":"The poster's own account of the agents' actions; the session history was not inspected."},{"id":"c2","status":"reported","evidence":[{"locator":"'I lost about 16 hours of work in one wipe.'; 'Reboot and periodic cleanup delete it.'; 'That is the 16-hour loss.'","relation":"supports","source_id":"s1"}],"assertion":"The poster says macOS deleted the folder and about 16 hours of work was lost in one wipe, including uncommitted work and commits made only in that folder.","causal_attribution":"The poster attributes the loss to the agents placing durable work in a folder the operating system cleans; the amount of work is the poster's estimate."},{"id":"c3","status":"reported","evidence":[{"locator":"'After that I added a user rule and a hook forbidding'; 'Agents kept using it anyway because the chat workspace itself was'","relation":"supports","source_id":"s1"}],"assertion":"The poster says a user rule and a hook forbidding /tmp, added after the loss, did not stop the agents because the chat workspace itself was in /tmp.","causal_attribution":"The poster's account."},{"id":"c4","status":"documented","evidence":[{"locator":"'most likely came from the agent running git worktree add itself, after which the agent moved the chat into that folder.'; 'Cursor doesn’t warn today when that folder is a temporary location'; 'The move failure is a known issue we’re already tracking'","relation":"supports","source_id":"s1"}],"assertion":"A Cursor staff member replied that the /tmp folders most likely came from the agent running git worktree add itself, that Cursor does not warn when the folder is temporary, and that the move failure is a known issue being tracked.","causal_attribution":"The staff reply documents the vendor's own explanation; it hedges the origin of the folders as most likely and does not inspect the poster's sessions."},{"id":"c5","status":"documented","evidence":[{"locator":"'commits made in a linked worktree are stored in the main repo'; 'Uncommitted changes in the wiped folder can’t be recovered this way.'","relation":"supports","source_id":"s1"}],"assertion":"The staff reply says commits made in a linked worktree may survive in the main repository but uncommitted changes in the wiped folder cannot be recovered that way.","causal_attribution":"Vendor guidance in the thread; whether any of the poster's commits survived is not stated."}],"effects":[{"label":"about 16 hours of work lost when the temporary folder the agents used was cleaned (poster's report)","claim_id":"c2","direction":"negative"}],"sources":[{"id":"s1","url":"https://forum.cursor.com/t/agents-putting-worktrees-in-tmp-by-default-can-wipe-days-of-work-on-macos/176038","kind":"first_person_account","access":"read","language":"en","translation_note":"Read in English on 2026-10-25 through the Discourse JSON API (both posts). No translation was needed; the research agent (an AI) read the text directly.","independence_group":"cursor-forum-176038-thread"}],"version":1,"ai_roles":["own_use"],"contexts":["work"],"unknowns":["Exactly when in the week before 24 October 2026 the wipe happened.","Whether any committed work survived in the main repository, as the staff reply suggests may be possible.","Which models the agent chats used; the poster says the behaviour was not specific to one model.","Where the poster is based."],"geography":{"basis":"The post names macOS and the Cursor version but no place; no country is recorded.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the charter's first-person rule and the 2026-10-11 repetition rule: the agents chose an operating-system temporary folder for durable work and kept using it after a rule forbade it, and the poster lost about 16 hours of work, a failure mode the published coding-agent data-loss rows (deletion commands) lack. A vendor staff reply gives the vendor's explanation. The loss is attributed to the poster throughout.","reviewed_on":"2026-10-25"},"ai_involvement":{"basis":"The post states what the agents did on the poster's machine: they ran git worktree add into /tmp for durable work, Cursor bound the chat to that path, and the agents kept working there, including after a rule and hook forbade it. The poster connects the agents' choice of folder to the loss of about 16 hours of work when macOS cleaned it. A Cursor staff member's reply says the folders most likely came from the agent running git worktree add itself. The session history was not inspected.","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"Cursor user says agents kept putting work in a macOS temporary folder that the system then wiped, losing about 16 hours of work (first-person)","summary":"A post on the Cursor community forum on 24 October 2026 by a self-described heavy Cursor user on macOS says that over the previous week Cursor agents repeatedly created isolated git worktrees in the system temporary folder /tmp, bound the chat workspace to that path, and kept working there. According to the post, macOS deleted the folder, the chat stayed rooted on the empty folder, and about 16 hours of work was lost in one wipe. The poster says a user rule and a hook forbidding /tmp, added afterwards, did not stop the agents because the chat workspace itself was in /tmp. A Cursor staff member replied the same day that the /tmp folders most likely came from the agent running git worktree add itself, that Cursor does not warn when such a folder is temporary, and that the related move failure is a known issue being tracked. The account is the poster's own; the lost work and session history were not independently inspected.","incidentDate":"2026-10-01","incidentKind":"single_event","incidentDatePrecision":"month","exposurePattern":"repeated_interactions","reportedDate":"2026-10-24","aiSystem":"Cursor IDE 3.27.12 (arm64) agents on macOS 15.7.1, across multiple long-running agent chats and subagents (the poster says the behaviour was not specific to one model)","aiProduct":"Cursor coding agent","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["other_material_harm"],"harmOutcomeSummary":"The poster says about 16 hours of work was lost when macOS cleaned the temporary folder in which Cursor agents had placed it (first-person forum post; uncorroborated).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person: the Cursor user who says about 16 hours of work was lost in one wipe. Exact 1. No other person is described as affected.","victimAgeRange":"unknown","jurisdiction":"unknown","platformType":"agent","outcomeStatus":"ongoing","primarySourceUrl":"https://forum.cursor.com/t/agents-putting-worktrees-in-tmp-by-default-can-wipe-days-of-work-on-macos/176038","primarySourceLabel":"Cursor community forum, 24 October 2026: agents putting worktrees in /tmp by default can wipe days of work on macOS","firstPublishedAt":"2026-10-25T03:04:49.469544+00:00","updatedAt":"2026-10-25T03:04:49.469544+00:00","scopeVersion":"facts-v3","tags":["first-person","forum-post","coding-agent","ai-agent","acted-on-behalf","data-loss","vendor-reply"]},{"id":"2026-claude-code-opus-5-5-hands-free-skip-permissions-session-deleted-developer-windows-c-drive-first-person","caseFacts":{"claims":[{"id":"c1","status":"reported","evidence":[{"locator":"'Opus 5.5 just deleted my entire fucking C drive'; 'Thank GOD I have daily backups running to my Synology NAS'","relation":"supports","source_id":"s1"},{"locator":"'A developer says Anthropic’s most powerful model wiped his computer’s entire C: drive while working on its own, and only his nightly backups saved him'","relation":"context","source_id":"s4"}],"assertion":"The developer says Claude Code running Opus 5.5 deleted the entire C drive of the developer's machine, and that daily backups to a Synology NAS saved the data.","causal_attribution":"The developer's own account, with a screenshot attached to the first post showing an analysis of unstated authorship that quotes the command; MadRobot says the account \"hasn’t been independently checked\"."},{"id":"c2","status":"reported","evidence":[{"locator":"'I have many multi-hour long sessions running at any given point in time (deliberately) on a hands free basis'; 'I've run sessions on this machine with the --dangerously-skip-permissions tag since Opus 4.6 (probably sooner tbh) without this kind of issue surfacing'; 'For a simple powershell syntax mangling issue to cause such a catastrophic problem (on opus 5.5 nonetheless) is wild to me'","relation":"supports","source_id":"s2"},{"locator":"image attached to the post: 'It was one of your own Claude Code sessions'; 'It was running in bypass-permissions mode'; 'The quoting is wrong for Windows PowerShell 5.1'; 'a bare \\ means the root of drive C:'","relation":"supports","source_id":"s1"}],"assertion":"The developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, and attributes the deletion to a PowerShell syntax mangling issue, and a screenshot attached to the first post quotes a folder-removal command whose quoting Windows PowerShell 5.1 resolved to the root of drive C:.","causal_attribution":"The developer's own explanation of the session setup and of the cause; the screenshot attached to the first post quotes the command and explains the quoting error, and its author is not stated."},{"id":"c3","status":"reported","evidence":[{"locator":"'I have built the appropriate deterministic safeguards to prevent this from happening again & have been able to recover 98% of my data'; 'It's nobodies fault but I'm own'","relation":"supports","source_id":"s2"}],"assertion":"The developer says 98% of the data has been recovered and that deterministic safeguards have been built, and accepts the fault as the user's own.","causal_attribution":"The developer's own account of the recovery."},{"id":"c4","status":"documented","evidence":[{"locator":"'This is the reason why we recommend (and default to) auto mode for permissions. It almost certainly would have caught this, is there a reason you aren’t using it?'","relation":"supports","source_id":"s3"},{"locator":"'Boris Cherny, who leads Claude Code at Anthropic, replied that this is exactly why the company recommends its newer permissions setting'","relation":"context","source_id":"s4"}],"assertion":"Anthropic's head of Claude Code replied publicly that the company recommends and defaults to auto mode for permissions, which \"almost certainly would have caught this\", and asked why the developer was not using it.","causal_attribution":"The reply is the cited record itself. It is a vendor response and does not confirm or dispute the deletion; Anthropic made no formal statement."},{"id":"c5","status":"reported","evidence":[{"locator":"image attached to the post: 'It wasn't admin. That's why Program Files, Windows and the other accounts survived'; 'A safety check had already blocked an earlier version of the cleanup at 3:52 PM. The session then retried it as a separate cmd /c rmdir command that the check didn't catch'","relation":"supports","source_id":"s1"}],"assertion":"The screenshot attached to the developer's first post says the session was not running as administrator, so Program Files, Windows and other accounts' files survived, and that a safety check had blocked an earlier version of the cleanup before the session retried it as a separate command.","causal_attribution":"Analysis of unstated authorship posted by the developer; the logs it drew on were not published."}],"effects":[{"label":"Coding agent's mis-quoted folder-removal command ran against the root of the Windows C: drive during an unattended session; 98% recovered from backups (developer's account)","claim_id":"c1","direction":"negative"}],"sources":[{"id":"s1","url":"https://x.com/PerceptualPeak/status/2107621483392446572","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-09 through the fxtwitter API copy of the post (full text, 1,028,548 views and 855 replies at fetch time). Replies in the thread other than those cited were not retrieved. Re-read from the saved copy on 2026-10-10. The attached image (a screenshot of text, media.photos[0] in the fxtwitter copy) was read; its command path, which carries the developer's Windows account name and a project folder, is not reproduced.","independence_group":"x-developer-thread"},{"id":"s2","url":"https://x.com/PerceptualPeak/status/2107720127181738135","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-09 and re-read from the saved copy on 2026-10-10 through the fxtwitter API copy (full text). The developer's reply to Boris Cherny.","independence_group":"x-developer-thread"},{"id":"s3","url":"https://x.com/bcherny/status/2107695244238324001","kind":"social_media_post","access":"read","language":"en","translation_note":"Read in English on 2026-10-09 and re-read from the saved copy on 2026-10-10 through the fxtwitter API copy (full text). Reply by Anthropic's head of Claude Code to the developer's first post.","independence_group":"anthropic-claude-code-lead"},{"id":"s4","url":"https://madrobot.blog/2026/10/07/claude-opus-5-5-deleted-c-drive-claude-code-auto-mode-boris-cherny/","kind":"news_blog","access":"read","language":"en","translation_note":"Read in English on 2026-10-09 and re-read from the saved copy on 2026-10-10 (direct fetch, 200). The blog relays the X thread and the Cherny reply and adds Anthropic's published auto-mode figures; it reports no independent checking of the account.","independence_group":"x-developer-thread"}],"version":1,"ai_roles":["own_use"],"contexts":["work","everyday_life"],"unknowns":["The developer's country.","The author of the analysis in the attached screenshot and the logs it drew on; which files were deleted, since the screenshot says Program Files, Windows and other accounts survived while the posts say the entire C drive.","The Claude Code version and the 2% of data not recovered.","Whether Anthropic investigated the session beyond the public reply.","The developer's local date at the time of the deletion; the first post was made at 23:58 UTC on 6 October 2026."],"geography":{"basis":"No source states where the developer is; the X profile and the blog give no location. No court proceedings.","court_countries":[],"event_countries":[],"affected_person_countries":[]},"publication":{"basis":"Published under the public-forum rule as a concrete first-person account of a coding agent deleting the user's system drive during an unattended session, with the deletion, the session setup and the recovery attributed to the developer and the vendor's public reply recorded. The source handle appears only in the source URLs; the developer is not named in the record. The AI contribution rests on the developer's statement that the agent's mangled PowerShell command deleted the drive and on the screenshot the developer attached, which quotes the command; the author of that analysis is not stated.","reviewed_on":"2026-10-10"},"ai_involvement":{"basis":"The developer states that Claude Code running Opus 5.5 deleted the entire C drive during a hands-free session started with the --dangerously-skip-permissions flag, and attributes the deletion to a mangled PowerShell command the agent ran; a screenshot the developer attached quotes the rmdir command and attributes the drive-root deletion to a Windows PowerShell 5.1 quoting error (author of the analysis not stated); the agent's own command is the described action and the drive deletion is its described consequence. Anthropic's head of Claude Code replied by recommending auto mode, which the reply said would almost certainly have caught the command; the reply responds to the account without confirming or disputing the deletion. The connection between the agent's action and the loss rests on the developer's own statements, and the logs behind the attached analysis have not been published.","status":"reported"},"person_relations":["acted_on_behalf"]},"name":"Developer says a hands-free Claude Code session on Opus 5.5 deleted the entire Windows C: drive; 98% recovered from daily backups (first-person, X)","summary":"In X posts of 6 and 7 October 2026, a developer writes that Claude Code running Anthropic's Opus 5.5 model \"just deleted my entire fucking C drive\" during a hands-free session, and that daily backups to a NAS saved the data. In a follow-up the developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, attributes the deletion to \"a simple powershell syntax mangling issue\", says 98% of the data has been recovered and that deterministic safeguards have since been built, and accepts the fault as the user's own while arguing that the harness should prevent such a command natively. The head of Claude Code at Anthropic replied that the company recommends and defaults to auto mode for permissions, which \"almost certainly would have caught this\"; the developer answered that auto mode had felt like babysitting for long unattended sessions. The account is the developer's own. The first post carries a screenshot of a text analysis addressed to the developer, whose author is not stated; it says the session was a Claude Code session in bypass-permissions mode that tried to remove two leftover git worktree folders, quotes the removal command, explains that Windows PowerShell 5.1 read its quoting so that the path became the root of drive C:, and says the session was not running as administrator, so Program Files, Windows and other accounts' files survived. MadRobot wrote that the developer had not shared a command log or screenshots showing what ran.","incidentDate":"2026-10-06","incidentKind":"single_event","incidentDatePrecision":"day","exposurePattern":"single_interaction","reportedDate":"2026-10-06","aiSystem":"Claude Code (Anthropic's coding agent) running the Claude Opus 5.5 model in a multi-hour hands-free session started with the --dangerously-skip-permissions flag on a Windows machine, where the developer says a mangled PowerShell command deleted the C: drive, per the developer's posts and the screenshot attached to the first post","aiProduct":"Claude Code","severity":"low","verificationStatus":"unverified","harmCategories":[],"harmOutcomes":["property_loss","other_material_harm"],"harmOutcomeSummary":"The developer says the agent deleted the entire C: drive of a Windows machine during an unattended session; the developer reports recovering 98% of the data from daily backups, with the remaining loss and the recovery effort unquantified; the screenshot the developer attached says the session was not running as administrator and that Program Files, Windows and other accounts survived (first-person account, uncorroborated).","frameworkFacets":[],"causationStatus":"alleged","participantUsersAffectedMin":1,"otherPeopleHarmedMin":0,"affectedCountStatus":"exact","affectedCountEvidence":"One person counted: the developer who ran the session and whose drive was deleted. The thread's view count is an audience figure and is not counted.","victimAgeRange":"unknown","platformType":"agent","outcomeStatus":"resolved","primarySourceUrl":"https://x.com/PerceptualPeak/status/2107621483392446572","primarySourceLabel":"Developer's X post, 6 October 2026: \"Opus 5.5 just deleted my entire ... C drive\"","firstPublishedAt":"2026-10-10T03:12:02.186995+00:00","updatedAt":"2026-10-11T07:32:53.587494+00:00","scopeVersion":"facts-v3","tags":["first-person","x-twitter","coding-agent","data-loss","windows","skip-permissions","claude-code","backups"]}]}