Claude Code Self-Audit Finds 3GB of Cruft in ~/.claude — Here's How to Clean It
A Reddit user fed Claude Code a forensic audit prompt to investigate why it felt sluggish. The tool found 3GB of accumulated cruft in ~/.claude and project-level CLAUDE.md files. After cleanup, the directory shrank to under 200MB.
The Prompt Used
Do a forensic audit of my ~/.claude directory and any project-level CLAUDE.md files in my workspace. I suspect accumulated cruft is degrading performance. Report:
For each finding, explain WHY it impacts performance (disk I/O at startup vs. context-window bloat vs. retry loops) and give me safe find / rm commands to clean it up. Don't execute anything — just report.
Findings in the User's Environment
- 2.6 GB in
projects/— 9,318 JSONL session transcripts across 172 project dirs, never purged. Causes disk I/O at startup. - 170 MB in
telemetry/— 91 files of1p_failed_events.*from a silent retry loop where telemetry couldn't reach the endpoint and kept buffering. - 153 MB of file-history undo buffers.
- 3,095 stale todo JSON files — one per session/agent, ever.
- A 986-line
CLAUDE.md, plus a 346-line one insidenode_modulesthat loads whenever youcdnearby, causing context-window bloat. - Stacked
CLAUDE.mdfiles in nested backend dirs adding up to ~900 lines of context just by being in a subdirectory.
What to Do
The user didn't share exact cleanup commands, but the audit report gave safe find/rm suggestions. You can craft your own based on the findings: remove old session transcripts from ~/.claude/projects/, delete telemetry retry buffers, prune undo buffers, and collapse or truncate bloated CLAUDE.md files — especially those in node_modules or deeply nested directories.
📖 Read the full source: r/ClaudeAI
👀 See Also
iCloud Desktop/Documents Sync Causes File Loss Issues with Claude on Mac
A Mac user reports that enabling iCloud Drive sync for Desktop and Documents folders causes Claude to create duplicate files and can lead to permanent data loss, including hidden /.claude folders that iCloud doesn't back up.
How to Prevent CLAUDE.md Rot: Treat Rules Like Code
After 18 months of real-world use, one developer shares four disciplines to keep CLAUDE.md under 100 lines: use it as an index, separate rules from sources, audit on every PR, and delete more than you add.
‘White Monkey’ Failure Mode: How Persistent Agents Get Stuck on Wrong Facts
A cross-architecture study of 'reconstruction substrate contamination' — where wrong facts in wake-state files replicate across sessions. Includes a 6-question survey for persistent agents.
Claude Code: Context Management Over Prompt Engineering
A developer shares that after a year of using Claude Code, the key skill isn't prompt wording or model selection, but providing comprehensive project context upfront to get better results.