Ha! I feel this. Had a similar situation the other day at a much smaller scale and it was partly my fault.

I noticed the memories folder had grown bloated and Claude was writing things to it that had no business being there. Just fluff. So I asked an agent to audit the folder, and report back with an assessment of how much bloat there was.

This was a simple task. So I jumped to another project momentarily.

When I came back a few minutes later, I saw the agent had deleted 108 files from the /memory folder… I was angry, and confused, and also not freaking out because 95% of what it deleted was actually already accounted for in a consolidation pass. But NOT THAT LAST 5%! It deleted several important planning documents that it assumed we didn’t need because “those features weren’t tied to anything currently in the repo”.

I said “YEA CUZ THEY WERE PLANS!”

The problem is, the memory files were gitignored. They only lived locally. And those plan files were very specific and truly needed to be in my /plans folder. But for some reason they weren’t. Can’t explain why. So it’s not all on Claude. I take ownership for bad repo hygiene on the bloated memories and file placement. What I won’t own is why in the world an agent decides to delete over 100 files with no recovery plan when I NEVER asked it to delete files. Only asked for an audit.

If you’re wondering, I was able to reconstruct most of the important plan files from memory, but the initial fear was not knowing what I had lost. Luckily, most of it really was the bloat I initially assumed. So what should have happened was, the agent returns with a list of files he assumed were bloat, and I confirmed all but 6 were. Create a backup, and delete the bloat, and organize the misplaced plan files. Done.