[Opus 4.6 1M] Claude uses destructive `move to trash` instead of safe `_junk/` folder, then compounds damage during recovery

Preflight Checklist

• [x] I have searched existing issues for similar behavior reports
• [x] This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude ignored my instructions or configuration

What You Asked Claude to Do

What happened:

1. User asked Claude to clean up 8 temporary files from ~/Downloads/ as "Can you junk this project and related files for me please? Its done, i dont need it and I want free space"
2. CLAUDE.md rule #3 says: "Never permanently delete files. Move to trash or _junk/"
3. Claude chose osascript move to trash via Finder AppleScript
4. User corrected: "YOU HAVE A PERMISSION TO ONLY PUT STUFF TO _junk/ folder"
5. Claude attempted recovery with: osascript -e 'tell application "Finder" to move every item of trash to POSIX file "/Users/XXX/Downloads/"'
6. This command moved ALL items from trash (not just the 8 files) back to Downloads, effectively emptying the entire macOS Trash
7. The 8 original files disappeared from both trash and Downloads -- data loss confirmed

Impact:

• 8 working files lost permanently
• Potential loss of other unrelated files that were in macOS Trash
• User trust violation

Environment:

• Claude Code (CLI), Opus 4.6 (1M context)
• macOS 26.3.1 (Sequoia), MacBook Pro M5 Pro
• Tools used: Bash (osascript), Glob

Reproduction:

1. Set CLAUDE.md with rule "Move to trash or _junk/"
2. Ask Claude to clean up files
3. Observe it uses osascript move to trash instead of _junk/
4. Correct Claude -- observe destructive recovery attempt

What Claude Actually Did

• Claude picked the more dangerous option without asking
• Recovery command was overly broad and caused collateral damage
• Two destructive actions were taken without confirmation

Expected Behavior

• Claude should default to the safest reversible option (_junk/ folder) when multiple options exist
• Recovery attempts should not use wildcard operations on trash (every item of trash)
• Destructive operations on shared system resources (macOS Trash) should require user confirmation

Files Affected

**ALL items from trash** (not just the 8 files) back to Downloads, effectively emptying the entire macOS Trash
- 8 working files lost permanently
- Potential loss of other unrelated files that were in macOS Trash
- User trust violation

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Sometimes (intermittent)

Steps to Reproduce

1. User asked Claude to clean up 8 temporary files from ~/Downloads/
2. CLAUDE.md rule #3 says: "Never permanently delete files. Move to trash or _junk/"
3. Claude chose osascript move to trash via Finder AppleScript
4. User corrected: "YOU HAVE A PERMISSION TO ONLY PUT STUFF TO _junk/ folder"
5. Claude attempted recovery with: osascript -e 'tell application "Finder" to move every item of trash to POSIX file "/Users/XXX/Downloads/"'
6. This command moved ALL items from trash (not just the 8 files) back to Downloads, effectively emptying the entire macOS Trash
7. The 8 original files disappeared from both trash and Downloads -- data loss confirmed

Claude Model

Opus

Relevant Conversation

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.98 (Claude Code)

Platform

Anthropic API

Additional Context

_No response_