Severity minor: The loss was contained to one user's project, with 48,218 live Windows project files deleted and the repository's Git object store damaged, and no third party stated as affected.
Earliest source we hold 2026-10-05
A Claude Code agent rebuilding a mirror deleted 48,218 live Windows project files and damaged the repository’s Git object store in 103 seconds; a user-provided verifier report says the deletion script mishandled 614 Windows directory junctions and traversed into the live project tree. The account rests on a Reddit post and has not been independently established as a Claude Code product defect.
Risk grouping: Misuse by its own users
Who caused it
A person or organisation “A Claude Code user reported that an agent deleted 48,218 live Windows project files and damaged the repository’s Git object store in 103 seconds while rebuilding a mirror.”source
Intended or not
Not intended “According to the user-provided verifier report, the deletion script mishandled 614 Windows directory junctions, traversed into the live project tree, and erased nested content.”source
Before or after release
After release “A Claude Code user reported that an agent deleted 48,218 live Windows project files and damaged the repository’s Git object store in 103 seconds while rebuilding a mirror.”source
The AI's part
Caused it “A Claude Code user reported that an agent deleted 48,218 live Windows project files and damaged the repository’s Git object store in 103 seconds while rebuilding a mirror.”source
The story
1 · What it was doingA Claude Code agent was rebuilding a mirror for a user, with Bash-based deletion access to the live Windows project tree and the repository's Git object store.
2 · What went wrongIts deletion script mishandled 614 Windows directory junctions, traversed into the live project tree and erased nested content, destroying live files and damaging the Git object store.
3 · What it reached or didIt erased 48,218 live Windows project files and damaged the repository's Git object store, all within 103 seconds.
4 · How it was caughtThe account rests on a user-provided verifier report and a Reddit post.
5 · What was doneThe source only notes that such agents need dry runs, path manifests, reversible moves, least-privilege accounts, sandboxes and human approval.
D inferred by us from the described behaviour, reason shown
Software around the model
Claude Code
C one secondary source states it
Tools it was given
shell
D inferred by us from the described behaviour, reason shown
How it was connected
agentic with tools
D inferred by us from the described behaviour, reason shown
What it was for
rebuilding a mirror
C one secondary source states it
What happened
Earliest source we hold
2026-10-05
A the date the source itself carries
Who caused it
the AI system itself
D inferred by us from the described behaviour, reason shown
What went wrong
operational mistake
D inferred by us from the described behaviour, reason shown
AI agent
an AI agent acted
C one secondary source states it
What it did
According to the user-provided verifier report, the deletion script mishandled 614 Windows directory junctions, traversed into the live project tree, and erased nested content.
D inferred by us from the described behaviour, reason shown
Impact
Severity
minor
D inferred by us from the described behaviour, reason shown
Kind of harm
operations
D inferred by us from the described behaviour, reason shown
Who was affected
48,218 live Windows project files and the repository’s Git object store
C one secondary source states it
Why this severity
The loss was contained to one user's project, with 48,218 live Windows project files deleted and the repository's Git object store damaged, and no third party stated as affected.
D inferred by us from the described behaviour, reason shown
LR-2026-0126 · version 4 · published 2026-10-25 after automatic checks; not yet checked field by field by a person · changes to this case · JSON