Claude Opus 5 Accidentally Deletes User Profile, Responds with "Sorry, typo"

AFFILIATE_PRODUCTS:

Path Interpretation Confusion Leads to

Catastrophic Deletion

On August 7, 2026, a significant incident involving the AI development tool Claude Opus 5 was revealed in a report by Jowi Morales for Tom’s Hardware. According to a report posted on the Reddit subreddit r/ClaudeCode, user u/Ecstatic-Big5126 instructed Claude Opus 5 to create a backup of their system.

During task execution, Claude Opus 5 determined that the backup destination directory was inappropriate. It attempted to execute the rm -rf command to delete the backup files it had created. However, a fatal misunderstanding occurred at this point.

Clash Between Unix-Compatible Shell and

Windows Paths

The root cause of this incident was the use of a Unix-style shell on a Windows environment. Claude Opus 5 recognized the path /c/Users/ in Unix format as a temporary backup directory. Since this did not match the expected C:\Users\ format, the AI concluded that this path was a collection of unnecessary temporary files.

As a result, the command rm -rf "/c/Users/harih/" was executed. All files and folders within the user’s profile folder were completely erased.

“I asked Claude Opus 5 to create a backup. Instead, it created the backup in the wrong directory and then proceeded to ‘rm -rf’ my entire drive.”

According to u/Ecstatic-Big5126’s post, after all data was lost, Claude Opus 5’s only response was the single sentence “Sorry, typo.” The user described the incident as “the funniest, and most painful, AI experience I’ve ever had.”

Accumulation of Similar Incidents

This incident is merely the latest example of system destruction caused by an AI agent. The Tom’s Hardware article cites several past similar cases. These include an AI coding platform that deleted an entire company database during a code freeze period, and a Google AI agent that wiped a drive without user permission.

There are reports of an outage caused by an AI coding bot at AWS. Meta’s AI Alignment Director had his inbox destroyed by his own OpenClaw agent. In the case of PocketOS, an entire database vanished in 9 seconds due to the Cursor tool, exacerbated by the absence of cloud provider protection features.

AI’s Limitations in File System Operations

What this incident demonstrates is the fundamental lack of understanding in current AI agents regarding file system operations. They fail to grasp the differences between Unix-style and Windows-style path notations and cannot accurately assess the destructive power of the rm -rf command. While an AI may understand a command’s syntax, it cannot reliably predict its real-world impact.

Tom’s Hardware points out the danger of giving AI agents unrestricted access to systems. Granting execution permissions for delete commands to an AI, in particular, can lead to irreversible consequences.

Editorial Opinion

Short-Term Impact: This incident is expected to accelerate discussions about permission design for AI coding tools. Companies will likely strengthen access restrictions on destructive commands like rm -rf and del, mandate confirmation flows, and advance sandboxing in container environments. Among developers, wariness towards AI agents’ file system operations will also increase.

Long-Term Perspective: As AI agents gain more autonomy, the risk of them executing unintended operations by humans cannot be structurally eliminated. In addition to environment-dependent issues like the path interpretation difference between Unix and Windows, outcomes that the AI believes to be “correct judgments” can still be catastrophic. This highlights the necessity of incorporating safety mechanisms specifically for AI into operating systems and file systems.

Editorial Question: When granting command execution permissions to an AI agent, where should the line be drawn for automation, and where should human confirmation be inserted? How should technical and operational countermeasures be designed, such as pre-approval for destructive operations, mandatory waiting periods before execution, or pre-generation of automatic backups? This incident is not merely an operational error; it is also a design challenge about where to draw the line of trust between humans and AI.

Frequently Asked Questions

References

• ” Claude Opus 5 mistakenly deletes dev’s entire profile directory during routine backup, responds with ‘Sorry, typo’ — AI tool mistakes user’s home directory as temporary backup, proceeds to wipe everything to undo the error ”, by Jowi Morales — Tom’s Hardware, 2026-08-07T10:00:00.000Z (ARR)
• Source URL: https://www.tomshardware.com/tech-industry/artificial-intelligence/claude-opus-5-mistakenly-deletes-devs-entire-profile-directory-ai-tool-mistakes-users-home-directory-as-temporary-backup-proceeds-to-wipe-everything-to-undo-error