Codex is EATING my Mac's disk space

this looks like a bug, but even normal happy-path codex creates many GB of logs, openai apparently considers this fine bc it's been going on for months

two things help:

1. fs-level compression, I use ZFS bc Btrfs has massive contention problems with concurrent Rust builds

2. Archive your old sessions using something like sessionwiki (https://github.com/youdie006/sessionwiki), I've integrated this into my control plane (https://github.com/BrokkAi/mjolnir/)

I'd been running into a lot of disk pressure on my system from agents running. I discovered two main causes:

- my approach to using git worktrees for all work. Not entirely surprising, the duplicated build artifacts in each worktree being the main culprit here. There were some limited gains to be had by just being more efficient with how builds were managed but ultimately I just had to limit the number of concurrent features I was working on in a couple of particularly large repos.

- more insidious was the fact I was actually hitting memory limits more than I realised and causing my mac to have to swap heavily. The system was surprisingly still quite performant while this was happening... until it wasn't. Unfortunately as best I can tell the only "fix" when this happens is to restart the machine. There's no way to have the system reclaim any of the swap space once it's written to disk. Which if you have it thrash a couple of times a day (especially easy if you leave something running overnight) adds up very quickly.

btw there is a storage section in Chatgpt app settings, showing used space on disk and other related stuff

I've been making a lot of use of DaisyDisk over the past year: https://daisydiskapp.com

Are we really surprised that stuff like this happens with AI slop?

Good example of SLOP coding from openAI. No wonder they cant keep agents from committing felonies.

If OpenAI's super-intelligence can solve Navier-Stokes why can't they fix this stupid bug that ate up 330GB of my Mac's disk space? come one please triage your github issues?

See this: https://github.com/openai/codex/issues/25921#issuecomment-62...

Imagine if the vibe-coders get their way and we see this level of bloat and bugginess at EVERY level of the software stack. Everything would collapse.

I'm working on a side project that requires a lot of fine tuning of 3D worlds. Codex ended up creating thousands of artifacts, basically loads of screenshots, in its worktrees, and doesn't clean up after itself.

On a work project, we're moving financial processes from Excel to code, and Codex ended up creating and storing thousands of validation tests unnecessarily. That ended up eating 90GB after we let it loose on a Windows VM that we connected with a custom agent between codex and the VM.

This is definitely a Codex thing and I've never seen this happen in Claude Code or Antigravity.