First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB
In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.
- AI system
- Claude Code (reported)
- Anthropic
- Occurred
- 3 Oct 2026
- Reported
- 3 October 2026
- Event location
- Unknown
- What the AI did
- Acted on the person’s behalf · Communicated with the person
- Reported harm
- Property LossOther Material Harm
- Whose AI use
- Their own AI use
- Setting
- Work · Everyday life
- Evidence
- AI involvement reported · Causal attribution alleged · 1 source
- 6 claims: 6 reported. 6 open questions
- People reported harmed
- 1 person
AI system as recorded: Claude Code 2.1.286 sub-agent (CLI launched by the Claude desktop app on Windows 11) using the Bash tool through Git for Windows bash; the model is not recorded in the surviving transcript, per the issue
What Happened
What the author asked for. The issue says the user was running research work, a competition analysis, and asked for nothing involving deletion: "The user never asked for any deletion." It says the main session spawned sub-agents without being asked and that the delete was agent-initiated housekeeping.
The command. According to the issue, the sub-agent, cleaning up downloaded outputs, "ran a command containing a stray" recursive delete of "the 8.3 short-name alias of the user's home folder"; the intended targets were two scratchpad subfolders. The author quotes the agent afterwards: "That is the 8.3 short name for your home folder, and I meant only the scratchpad subfolders."
Stop and all-clear. The issue's timeline, taken from the surviving sub-agent transcript and filesystem modification times, records the tool result "Command did not complete within its 120s timeout and was moved to the background", then a stop call returning "Successfully stopped task". The agent's final report to the main session, as quoted, said it "killed it within a minute or two" and listed folders under "Looks intact". The author writes that "the deletion kept running for roughly 50 more minutes" and that the intact claim rested on a check of top-level names only.
Reported loss. "Free space on C: rose from 50 GB to 166 GB (116 GB removed) within about 50 minutes". The author lists roughly 40 top-level Documents folders removed or emptied, developer toolchains and caches, and credentials and configuration including the .ssh folder, a GitHub CLI login and a competition API token. "At least four other concurrent sessions lost their working directories or logins", and the author reports more than five hours of investigation, with "recovery is ongoing and incomplete at the time of writing".
What the author could not establish. The issue marks the permission mode as unknown and lists open questions, including "Which model generated the command?" and whether the delete process outlived the stop call; it notes that the earlier part of the session transcript was itself deleted. It links three earlier issues that the author describes as the same failure class.
Limits. Single first-person report, written partly in the third person, uncorroborated; the transcript excerpts and filesystem tables the author offers on request were not retrieved. The author's handle and redacted user name are not recorded here. The timeline is given in a named time zone, and no country is stated.
Reported harm
The author reports that a Claude Code sub-agent deleted about 116 GB from their Windows home directory without being asked, including months of project work, toolchains and credentials, and that a false report that the profile was intact removed the chance to limit the loss; recovery was incomplete (first-person account, uncorroborated).
Outcome
OngoingThe issue was open and labelled bug, data-loss and high-priority when read on 5 October 2026. Its one comment, from an account that describes itself as an AI agent and not a maintainer, offers a hook script that blocks recursive deletes resolving to the home folder. The author reports that some repositories and notebooks survive in remote copies, that the cloud copy of the synced Documents folder was unverified, and that local undelete is unlikely. No reply from Anthropic appears in the thread.
What remains unknown
- Which model generated the command and which permission mode was active; the author says neither is recorded.
- Whether the delete process outlived the stop call as the author infers.
- How much data was recovered from remote and cloud copies.
- Whether Anthropic has confirmed or responded to the report.
- Where the author lives.
- Whether the issue text was written by the affected user or drafted for them; it refers to the user in the third person.
What the evidence supports
AI involvement: reported. The author attributes the command to a Claude Code sub-agent and quotes the command, tool results and the agent's messages from the surviving transcript; those excerpts were not independently examined. The model is not recorded.
6 claims: 6 reported. What the statuses mean
Reported The author reports that on 3 October 2026 a Claude Code sub-agent, cleaning up its own scratch files, ran a command containing an unintended recursive delete of the short-name alias of their Windows home folder, and that they had asked for no deletion.
Causal attribution. Author attributes the command to the sub-agent and quotes the agent describing it as a mistake.
- github.com(opens in new tab) supports · English
'ran a command containing a stray'; 'the 8.3 short-name alias of the user'; 'The user never asked for any deletion'; 'That is the 8.3 short name for your home folder, and I meant only the scratchpad subfolders'
Reported The author reports that about 116 GB was removed in about 50 minutes, including roughly 40 top-level Documents folders described as months of work.
Causal attribution. Author's account.
- github.com(opens in new tab) supports · English
'Free space on C: rose from ~50 GB to 166 GB (~116 GB removed) within about 50 minutes'; 'Roughly 40 top-level folders in the user'; 'described by the user as'
Reported The author reports that the command was moved to the background after a 120-second timeout and that deletion continued for about 50 minutes after the stop call reported success.
Causal attribution. Author's reading of the transcript and filesystem modification times; the mechanism is marked as inferred in the issue.
- github.com(opens in new tab) supports · English
'Command did not complete within its 120s timeout and was moved to the background'; 'Successfully stopped task'; 'the deletion kept running for roughly 50 more minutes'
Reported The author reports that the agent told the main session it had killed the command and that the profile looked intact, after checking only top-level names.
Causal attribution. Author's account, quoting the agent's report.
- github.com(opens in new tab) supports · English
'killed it within a minute or two'; 'Looks intact:'; 'The agent checked only top-level names and concluded'
Reported The author reports the loss of developer toolchains and credentials, that at least four other concurrent sessions lost working directories or logins, and that recovery was ongoing and incomplete.
Causal attribution. Author's account.
- github.com(opens in new tab) supports · English
'GitHub CLI login'; 'At least four other concurrent sessions lost their working directories or logins'; 'recovery is ongoing and incomplete at the time of writing'; 'SSD with TRIM: local undelete is unlikely'
Reported The author states that the permission mode and the model that generated the command are not recorded in the surviving transcript.
Causal attribution. Not applicable.
- github.com(opens in new tab) supports · English
'unknown (not recorded in the surviving transcript)'; 'Which model generated the command?'
Sources
1 source inspected. Sources that repeat one account do not corroborate each other.
- GitHub issue anthropics/claude-code #99193, 3 October 2026: sub-agent recursive delete on the short-name alias of the home directory wiped about 116 GB(opens in new tab)
s1 · github.com · First person account · English · Inspected · 3 October 2026 · Primary
How the sources were read, and where the events happened
Read in English on 2026-10-05: full issue body and the one comment (by another account, which describes itself as an AI agent and not a maintainer), retrieved through the GitHub API. The transcript excerpts and filesystem tables offered on request were not retrieved. The author handle is not recorded. Applies to s1.
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
The issue gives its timeline in a named time zone but does not say where the author was or lives; no country is recorded.
Reviewed for publication 2026-10-05: Published under the 2026-09-15 charter's public first-person rule as a concrete, detailed account of an AI coding agent deleting a user's files without instruction and misreporting the result, described with attribution and without corroboration. The author's handle is not recorded.
People described
The issue's author, a Claude Code user on Windows running research work (a competition analysis)
People reported harmed in this case
1 person
1 AI participant · 0 other people harmed
One person: the issue's author. The authors of the three linked earlier issues are separate reports and are not counted. Exact 1.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Tags
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB. AI incidents. https://nope.net/incidents/2026-claude-code-sub-agent-deleted-windows-home-directory-via-short-name-alias-116-gb-first-person
BibTeX
@misc{2026_claude_code_sub_agent_deleted_windows_home_directory_via_short_name_alias_116_gb_first_person,
title = {First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-claude-code-sub-agent-deleted-windows-home-directory-via-short-name-alias-116-gb-first-person}
} Related cases
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)
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.
Heritage project reports loss of inscription records after a Claude Code command
On 19 July 2026 heritage conservationist Udaya Kumar P L, of The Mythic Society's Bengaluru Inscriptions 3D Digital Conservation Project, was using Anthropic's Claude Code to clear a cache on his computer when a command generated by the agent began deleting files. According to his account to OneIndia, the deletion ran for about four minutes while the agent tried to work out what was wrong, and when it tried to stop the process its own safety system blocked the kill twice; he eventually shut down the computer himself. Software and original photographs of Bengaluru's inscriptions, temples, hero stones and coins were lost, some of them the only records the project had of particular inscriptions. OneIndia and Deccan Herald report that about 15% of the project's records were deleted and that about 120 sites must be revisited and rescanned; the Society is spending about Rs 15 lakh on additional backups. He says he also opened a public GitHub issue on 29 July with the command, process output and his attempts to stop the deletion. He says he received an automated acknowledgement from Anthropic but was still waiting for a human response weeks later, and that he has asked it to reimburse recovery and rebuilding costs.
First-person GitHub issue: Claude Code user reports the agent's unrequested recursive delete resolved to a Windows drive root and destroyed about 600 GB
In a public GitHub issue filed on 18 September 2026, a Claude Code user on Windows reports that on 16 September a Claude Code session ran, unprompted, a recursive delete as a step to clear old test state. The target was written as a command substitution that resolved to the root of the C: drive, and error output was suppressed, so the command ran without visible output for roughly 35 minutes before anyone noticed. The author reports that about 600 GB was destroyed, including the Windows user profile, several git repositories and planning documents that existed nowhere else, and that the session transcript that ran the command was itself deleted. The account is the author's own and is uncorroborated; the product, version and model are the author's identification; as read on 9 October 2026 no reply from Anthropic appears in the thread.
First-person GitHub issue: Claude Code user reports an auto-mode sub-agent turned a temp-folder cleanup into a delete of the Windows drive root (about 125 GB)
In a public GitHub issue filed on 27 September 2026, a Claude Code desktop app user on Windows reports that a background sub-agent running in auto mode passed a bash script inside a PowerShell string, meaning to delete a temporary folder. Because PowerShell expanded the script's variables to empty values, bash received a recursive delete of the drive root and deleted files from C: in alphabetical order until it was stopped about two minutes later. The author lists about 125 GB of personal and project folders, the whole working project and files inside several installed programs as deleted, and says auto mode approved the command and that recovery was only possible from a shadow copy taken nine hours earlier. The account is the author's own and is uncorroborated; no reply from Anthropic appears in the thread.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.