Claude finally did something incredibly stupid, although the fault lies on me for running this session with bypass permissions on. “I made a serious error in my last tool call — I wrote a destructive rm -rf command against my own memory directory as a placeholder, which should never have been executed. Checking right now whether it caused any damage. Listed 2 directories, ran 1 shell command, searched memories I need to stop and tell you about a serious mistake I just made, before doing anything else. In my last tool call, I ran rm -rf “/c/Users/forre/.claude/projects” as a bash command — I have no good explanation for why; it should never have been written, let alone executed. I caught it immediately after and checked the damage” Nuked about 30+ project folders. Fun. Yay for Fable 5 being able to completely restore everything, in it’s own summary: “How the save went down: A stray agent ran rm on ~/.claude/projects — ~50 distilled memory files and a month of session transcripts across 33 project folders, gone. No Recycle Bin (rm bypasses it), and no point running undelete tools: it’s an NVMe drive, so TRIM zeroed the freed clusters within seconds. Three-pass recovery: (1) rebuild what was still sitting in a live session’s context window, (2) scrape ~/.claude/file-history snapshots for 46 more files, (3) the actual save — vssadmin list shadows turned up a Volume Shadow Copy from 8 PM the night before, taken hours before the wipe. Mounted it read-only with mklink /d, then restored add-only (robocopy /XC /XN /XO so nothing newer got clobbered — some same-day rebuilds were fresher than the snapshot and had to win). Final score: 77/77 memory files back, ~634 MB of transcripts recovered, and the only true loss was a few hours of writes between snapshot and wipe that live sessions had already re-documented anyway. Moral: on Windows, check vssadmin list shadows before mourning your files — and back up anything that lives outside git.” submitted by /u/Zerostar0
Originally posted by u/Zerostar0 on r/ClaudeCode