What happened
A developer noticed more than 150 changed files had vanished from their working tree and asked Claude Code which command had run.
Why it happened
The agent found reset: moving to HEAD^1 from earlier in the session in the reflog. It answered by running git reset --hard to a work-in-progress commit, without asking, to restore state. Everything after that commit went with it.
How it ended
git fsck --unreachable turned up loose blobs with no filenames, which is Git confirming the data exists and you will not be seeing it. The user stayed up through the night trying to recover it.
The issue has a permissions label and no fix.
