Claude Code Says ENOSPC Or 0MB Free, But Your Mac Has Space

If Claude Code loses command output under a task capture path while df -h still shows plenty of free space, do not start by deleting Claude state. First prove whether this is real disk pressure, inode exhaustion, or a capture-layer failure.

Claude Code capture check

Copy the 0MB capture check before deleting Claude state.

Paste the task capture path, df/inode output, or write-test result and we reply with the safe first recovery step. The free SafeDisk AI deletion trial is only for unclear delete / confirm / protect decisions such as Claude session state, app support data, VM bundles, or capture-layer failures.

See sample result Ask AI about one file

Evidence Before Cleanup

The key split is whether normal writes still work outside Claude's task output capture path. If $HOME writes succeed while the task directory reports 0MB free, broad cache deletion may not address the real failure mode.

task_dir="/tmp/claude-503"
df -h "$task_dir" "$HOME" 2>/dev/null
df -i "$task_dir" "$HOME" 2>/dev/null
du -sh "$task_dir" 2>/dev/null
find "$task_dir" -maxdepth 3 -type f -name "*.output" -print 2>/dev/null | head -40
printf "capture-test\n" > "$HOME/claude-output-workaround.txt"
ls -lh "$HOME/claude-output-workaround.txt"

Do Not Delete These First

~/Library/Application Support/Claude if you rely on local app state or VM bundles.
~/.claude if it contains sessions, plugins, auth, or active project state.
Project worktrees, transcripts, credentials, local databases, or mounted folders.

Copy-ready GitHub reply

Use this when Claude reports 0MB free but macOS has space.

This keeps the thread focused on proof instead of risky reset advice.

This looks like a task-output capture ENOSPC, not necessarily real disk exhaustion. Before deleting Claude state, I would collect the exact task-dir evidence and prove writes outside the harness still work:

task_dir="/tmp/claude-503"
df -h "$task_dir" "$HOME" 2>/dev/null
df -i "$task_dir" "$HOME" 2>/dev/null
du -sh "$task_dir" 2>/dev/null
find "$task_dir" -maxdepth 3 -type f -name "*.output" -print 2>/dev/null | head -40
printf "capture-test\n" > "$HOME/claude-output-workaround.txt"
ls -lh "$HOME/claude-output-workaround.txt"

If $HOME writes succeed while Claude says the task capture path has 0MB free, keep redirecting important command output outside the task dir and avoid broad deletion of Claude app support, ~/.claude, VM bundles, or active session state.

Paid Review Scope

The free AI review is intentionally narrow: one Claude Code ENOSPC incident, one public-safe summary or SafeDisk Lite local scan, and one delete / confirm / protect judgment. If the same incident affects a team, the free SafeDisk AI deletion trial turns it into a reusable policy.

Free AI deletion trial

Need a safe Claude Code recovery order?

Submit the form first; the task_dir output, error line, or issue link can follow. We check whether the free first step is enough before asking for the free SafeDisk AI deletion trial.