[BUG] /private/tmp/claude-501 consumed 1.6TB on fresh macOS install with no actual usage

Resolved 💬 3 comments Opened Mar 13, 2026 by DasMonkey Closed Mar 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

Here's the full final bug report:

Title: [BUG] /private/tmp/claude-501 consumed 1.6TB after one day of active use via Cursor on fresh macOS install

Preflight Checklist

I have searched existing issues and this is a new occurrence worth documenting
I am using the latest version of Claude Code

What's Wrong?
On a brand new MacBook Pro M5 Pro (2TB, macOS 15), I installed Claude Code and used it via Cursor for approximately one day of active React Native / Expo development. I never manually cleared any temp files. Within one day, /private/tmp/claude-501 had consumed 1.6TB out of my 2TB drive, leaving only 341MB free and nearly making the machine unusable.
The exact cause is unclear — it may be Claude Code CLI, Claude Code running inside Cursor, or both. The temp folder was deleted before its contents could be inspected, so the specific files responsible are unknown.

Environment Info

Claude Code version: 2.1.74 (native installer)
Platform: macOS 15 (Apple Silicon M5 Pro)
Install method: curl -fsSL https://claude.ai/install.sh | bash
Also running Claude Code inside Cursor

Steps to Reproduce

Fresh macOS install on new MacBook Pro M5 Pro
Install Claude Code via native installer: curl -fsSL https://claude.ai/install.sh | bash
Follow PATH setup instructions
Use Claude Code via Cursor for active development on a React Native / Expo project for approximately one day
No manual cleanup performed
Check disk space: df -h /
Drive at 98% capacity with only 341MB remaining
Run sudo du -sh /private/tmp/* to find /private/tmp/claude-501 consuming 1.6TB

Discovery
bash# Checked free space
df -h /

Result: Avail 341Mi — 98% full

Narrowed down to tmp folder

sudo du -sh /System/Volumes/Data/private/*

Result: 1.7T /System/Volumes/Data/private/tmp

Found the culprit

sudo du -sh /private/tmp/*

Result: 1.6T /private/tmp/claude-501

Fixed by deleting

sudo rm -rf /private/tmp/claude-501

Result: Full 1.6TB immediately reclaimed

What's Unknown

Whether the temp files were generated by Claude Code CLI directly, Claude Code running inside Cursor, or both
The exact contents of /private/tmp/claude-501 — it was deleted before inspection to recover disk space
Whether it accumulated gradually during the coding session or had a runaway loop

What's Known

1.6TB accumulated in /private/tmp/claude-501 after approximately one day of active use
Deleting the folder immediately reclaimed all space
No warnings or alerts were shown at any point
This only became visible when the Mac nearly stopped functioning

Expected Behavior

Temp files written to /private/tmp/claude-* should be cleaned up automatically when a session ends or on startup
If disk usage grows unexpectedly, Claude Code should warn the user before it becomes critical
Under no circumstances should one day of normal usage consume 1.6TB of temp storage

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.74

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗