Are your coding agents quietly eating your disk?
by•
Since I started running Claude Code and Codex in parallel worktrees, my disk fills up much faster. Every worktree gets its own node_modules and build output, session logs pile up in ~/.claude and ~/.codex, and Xcode DerivedData does the rest.
I've seen people find 100GB+ of this stuff. How do you deal with it? Do you clean worktrees manually, script it, or just buy a bigger SSD?
13 views
Replies
Yeah I think node_modules in parallel worktrees are the sneaky bit. I tend to clean generated artifacts separately so a full disk doesn't turn into a bad source cleanup 😅
How do you decide when an AI coding agent is safe to let run fully on its own and when you still prefer to review everything manually
No more disk space, means no more extra space for memory ==> death
@garysz Exactly, and it gets slow before it breaks: macOS needs free disk for swap, so a full disk turns into a crawling machine. I now prune worktree build folders and node_modules right after merging.
We trusted an agent report with a confident disk usage number without checking it. The machine ran out of space anyway because the figure was just a hardcoded placeholder nobody had actually measured. It took a full day of digging to find out.