Re:Codex is EATING my Mac's disk space
by josephg on Saturday October 17, 2026 @09:08PM
(#50136836)
On Linux I’ve taken to disabling swap before doing memory heavy operations. Claude will carelessly run benchmarks and tasks which gobble up all available memory. When that happens, I’m not sure why but my system becomes unresponsive and I can’t kill the process. If I disable swap, the oom killer takes care of whatever Claude was doing and Claude figures it out after the fact.
[ Parent
| on HN ]
Re:Codex is EATING my Mac's disk space
by trollbridge on Saturday October 17, 2026 @10:02PM
(#50137130)
You can use systemd-oomd to force OOM killing without having to completely disable swap. It's quite handy for this especially since you can tell it to aim its OOM heavy artillery at only certain tasks (i.e. only processes that are descendants of claude-cli.)
One thing to also look out for is some distros will but /tmp in RAM, and claude loves to fill that
Re:Codex is EATING my Mac's disk space
by machomaster on Sunday October 18, 2026 @12:24PM
(#50142491)
Using Zswap might help you.