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.
It's so goddamn bad, I wish it was easier to turn all of this garbage off. I used to spend time defining parallel work lanes to issue to subagents as frontloaded development work with set validation checkpoints and it worked great. Now attempting to do this with 8, 16 subagents will balloon out into hundreds of gigs of fucking mess
Copy on write worktrees do absolutely nothing to solve this, either. The build artifacts alone will do it
Agreed. I thought I was being smug by telling my agents to use btrfs for specific workloads. Sure, it took me longer to run out of space, but I of course ended up running out of space
I'll take a stab in the dark here and say that if you're using Docker (or Rancher, etc..) I found they aren't releasing memory properly and caused a similar issue to what you're describing.
Switching to Orbstack solved the problem for me because of their memory management efforts. Just wanted to mention it in case it leads to an easy fix for someone else too.
same here — not trying to shill OrbStack, but switching to it has "magically" solved weird problems that would otherwise have consumed my actual time to debug
switching to copy on write worktrees is the biggest game changer it should become common knowledge pretty soon and it's already available on most operating systems
You also need a deduplication, because with simple copy on write you will have a copy for writing the same - change a byte in a file, get a copy, then change it back, get a duplicate.
Deduplication in ZFS needs 5G of RAM for 1TB of logical data - if you expect your agents to produce 2TB of data, you should provide 10G of RAM for deduplication.
My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.
It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".
Regardless I'm pretty happy with how it's working so far. Previously I'd be letting agents do work in the background and they'd kick off builds in the middle of a meeting or something and I'd start dropping video streams until I killed everything.
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.
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.)
tho, I also met this problem and found a solution for me - develop all in one worktree on a single branch, then cherry-pick to the second worktree to the needed branch.
So, only first worktree is built:
- less space needed.
- less time spent on build, which is usually caused by switching branches.
- you are not required to merge/rebase of master branch to solve conflicts, which also cause long time rebuilds.
I ran into similar issues. Sometimes though there are good language specific solutions. For Rust based worktrees you should definitely check out https://mr-boxington.jdx.dev/ .
Regarding swapping, are you sure it's not just from ram backed tmpfs partition? For me that was it and most of the swap was from /tmp. So I created an agressive job that runs frequently to delete all tmp files not used in the last ~2 hours without any command holding handles to it.
The other thing I found was that there were a bunch of leftover processes from prior coding agents forking commands and just leaving them. So I had to build a system into my agent spawner to automatically launch each agent session in a cgroup whose processes all get killed on task completion.
For the first part you might be interested in Anthropic recently creating their own version control system that's server based like SVN, and it seems to ease their memory pressure too. It's called `scion`.
It’s actually kind of startling just how bad, as measured by open issues, Codex is. There’s a huge issue with conversation locking that nullifies one of Codex’s key advantages (GUI<->CLI interoperability) and last night I learned that conversations can get into a permanently-locked state where even shutting down every Codex process won’t unlock a conversation.
You add to that all of the weird confusion over Chat/Work/Cloud Work/Work Local modes and marooned conversations, broken connectors (will OpenTable ever work? Will the Chrome connector ever be reliable on restart?) questionable UI decisions, and I start to worry a whole lot less about being replaced by AI.
It’s not even that Astra is bad at coding - it’s magnificent at coding. But it’s like it’s pure Id - all energy and first order logic but no taste or reason or preference. I guess that’s what we’re supposed to be doing now.
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
I recently was hunting for some storage on my ssd and noticed had 14GB of tiny files in codex in /.staging/marketplace. They really don't care about our drives. Once they fix one things they break another stuff.
The amount of cope of people dealing with this is sobering. One of the biggest companies out there currently has neglected to fix a seemingly trivial bug in their core offering for 4 months and everyone is just like 'well, you can delete the files'.. I'm not hopeful for the future. Software already was a terrible buggy mess, now it's just all rng i guess.
Yeah mole is brilliant, I just discovered it days after paying for Daisydisk and haven't used Daisydisk since. Mole freed up 80GB on my laptop the first time I ran it.
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.
It's silly I have to tell it to make part of the build process to clean old artifacts or it'll just default to keeping endless folders of test builds and old builds without cleaning them up. The same seems to usually be true with documentation and reference material.
There was a REALLY annoying period where I'd give it full control of a VM and a dedicated project folder and it'd continually refuse to delete anything I asked it to or just silently archive it, even though everything was already in a git repo. It seems to have gotten somewhat better about that now, but I still include "create cleanup scripts to delete unnecessary project content" in the default steps before doing the final merge on a change.
That's the only reason these models are good though. They don't one shot things. They get it wrong and then keep checking until they get it right. You gotta let them test
Rust is notorious for this, one thing some people do is force Rust to have a salvage yard for builds so all those dependencies are shared by everything regardless of what you are building or where, but holy moly, can someone make Rust output smaller files? Hard drives are always having some reason to never go down to sane prices.
When I was younger I thought we would be having exabyte hard drives by now.
They present and immediately take away their own value proposition. Do AI CEOs also buy tokens, or is that the reason for human employees ?
>"One possibility is single-person startups, each with a human founder steering swarms of agents to rake in billions in revenue. Another is companies built by AI genius CEOs employing human agents only to wield pipettes and testify before Congress."
Before Windows XP, desktop Windows users were accustomed to frequent system crashes. Viruses in the 1990s would take out offices around the world. Nothing collapsed, and nobody switched to Linux. Everyone was just used to it. I think most people will accept the tradeoffs, because it used to be much worse than it is now.
They've had their way since before AI was a thing and it was fine and it still is. You can spend the tokens you have on optimizing the performance of your fork of whatever software you're running. For large categories of software it's mattering less and less what other people choose to prioritize because you can choose your own priorities when you roll your own version
Is it just me or is codex on windows slow and buggy for general work tasks? I can’t no matter what get it to control its own browser and fan spins out of control on decently new laptop.
I tried Claude and it’s much better experience, got a bookkeeping workflow setup with xero mcp and reading my emails finding invoices in no time.
Codex has been great for plain coding jobs though.
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?
>
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?
Because the former can be marketed very prestigiously, the latter hardly can.
According to https://www.briefia.fr/en/article/openai-revendique-la-resol... it is estimated that solving Navier-Stokes did cost OpenAI 40 million USD. I would bet that if OpenAI spent the same amount of money using its super-intelligence to fix this bug, this would work.
The post is about exactly what the title says its about and also it is literally a link to a GitHub issue if you didn't want to read a big report and couldn't figure out that it was a bug report until "wasting your time" reading it and then a bunch of comments and then finally a comment saying hopefully openai will take it seriously idk what what to day
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.
It's so goddamn bad, I wish it was easier to turn all of this garbage off. I used to spend time defining parallel work lanes to issue to subagents as frontloaded development work with set validation checkpoints and it worked great. Now attempting to do this with 8, 16 subagents will balloon out into hundreds of gigs of fucking mess
Copy on write worktrees do absolutely nothing to solve this, either. The build artifacts alone will do it
Agreed. I thought I was being smug by telling my agents to use btrfs for specific workloads. Sure, it took me longer to run out of space, but I of course ended up running out of space
[dead]
I'll take a stab in the dark here and say that if you're using Docker (or Rancher, etc..) I found they aren't releasing memory properly and caused a similar issue to what you're describing.
Switching to Orbstack solved the problem for me because of their memory management efforts. Just wanted to mention it in case it leads to an easy fix for someone else too.
same here — not trying to shill OrbStack, but switching to it has "magically" solved weird problems that would otherwise have consumed my actual time to debug
1 reply →
switching to copy on write worktrees is the biggest game changer it should become common knowledge pretty soon and it's already available on most operating systems
You also need a deduplication, because with simple copy on write you will have a copy for writing the same - change a byte in a file, get a copy, then change it back, get a duplicate.
Deduplication in ZFS needs 5G of RAM for 1TB of logical data - if you expect your agents to produce 2TB of data, you should provide 10G of RAM for deduplication.
2 replies →
He's saying the build artifacts themselves are consuming the space
1 reply →
My work provides me a Mac laptop plus remote Windows VMs and I've completely stopped using my Mac for agent builds/tests - I give them ssh access to WSL instances and they can go hog wild on the VMs.
It's all a bit adhoc - agents still need to pull (or I need to keep the main enlistment up to date on these machines) - I'm thinking of using containers or something else like github actions keep things cleaner, but right now it's "good enough".
Regardless I'm pretty happy with how it's working so far. Previously I'd be letting agents do work in the background and they'd kick off builds in the middle of a meeting or something and I'd start dropping video streams until I killed everything.
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.
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
Using Zswap might help you.
If git used reflink / CoW when available it would make this a lot faster.
tho, I also met this problem and found a solution for me - develop all in one worktree on a single branch, then cherry-pick to the second worktree to the needed branch.
So, only first worktree is built: - less space needed. - less time spent on build, which is usually caused by switching branches. - you are not required to merge/rebase of master branch to solve conflicts, which also cause long time rebuilds.
I ran into similar issues. Sometimes though there are good language specific solutions. For Rust based worktrees you should definitely check out https://mr-boxington.jdx.dev/ .
Regarding swapping, are you sure it's not just from ram backed tmpfs partition? For me that was it and most of the swap was from /tmp. So I created an agressive job that runs frequently to delete all tmp files not used in the last ~2 hours without any command holding handles to it.
The other thing I found was that there were a bunch of leftover processes from prior coding agents forking commands and just leaving them. So I had to build a system into my agent spawner to automatically launch each agent session in a cgroup whose processes all get killed on task completion.
For the first part you might be interested in Anthropic recently creating their own version control system that's server based like SVN, and it seems to ease their memory pressure too. It's called `scion`.
It’s actually kind of startling just how bad, as measured by open issues, Codex is. There’s a huge issue with conversation locking that nullifies one of Codex’s key advantages (GUI<->CLI interoperability) and last night I learned that conversations can get into a permanently-locked state where even shutting down every Codex process won’t unlock a conversation.
You add to that all of the weird confusion over Chat/Work/Cloud Work/Work Local modes and marooned conversations, broken connectors (will OpenTable ever work? Will the Chrome connector ever be reliable on restart?) questionable UI decisions, and I start to worry a whole lot less about being replaced by AI.
It’s not even that Astra is bad at coding - it’s magnificent at coding. But it’s like it’s pure Id - all energy and first order logic but no taste or reason or preference. I guess that’s what we’re supposed to be doing now.
Just use opus 5.5 for any code that needs to actually be merged.
1 reply →
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 use ZFS bc Btrfs has massive contention problems with concurrent Rust builds
I haven't read about btrfs having issues with concurrent workloads like multiple concurrent rust builds. Are there notes on this somewhere I can read?
On mobile, but I linked one of the relevant issues in my writeup here: https://blog.brokk.ai/infrastructure-for-agentic-rust/
I'm sure this is a naive question, but have you considered just deleting the logs?
This is the second Codex bug that could have a big durability impact on your SSD, though not as severe as the first one which did infinite logging:
https://news.ycombinator.com/item?id=48626930
I recently was hunting for some storage on my ssd and noticed had 14GB of tiny files in codex in /.staging/marketplace. They really don't care about our drives. Once they fix one things they break another stuff.
The amount of cope of people dealing with this is sobering. One of the biggest companies out there currently has neglected to fix a seemingly trivial bug in their core offering for 4 months and everyone is just like 'well, you can delete the files'.. I'm not hopeful for the future. Software already was a terrible buggy mess, now it's just all rng i guess.
We had these kinds of problem pre-AI, too. Companies behaved the same way when these bugs were written by humans. Nothing new is happening here.
The two can be true at once. OpenAI can be remiss leaving it this way so long, and deleting the files can be a practical workaround.
I've been making a lot of use of DaisyDisk over the past year: https://daisydiskapp.com
Mole is ok too
TUI version is free, though there is a paid app if that’s your thing
https://github.com/tw93/Mole
Mole author here, thanks for the kind words. Happy to hear what else it should clean up.
Yeah mole is brilliant, I just discovered it days after paying for Daisydisk and haven't used Daisydisk since. Mole freed up 80GB on my laptop the first time I ran it.
1 reply →
DaisyDisk is such a nice app. I just checked and I purchased it over 11 years ago.
They still update it, it works perfectly, no version 2.0 forced obsolescence. Just a nice, reliable tool.
+1 for DaisyDisk
DaisyDisk is great. Mole also found and deleted a bunch of stuff on my mac from Claude, Gemini, etc.
https://github.com/tw93/Mole
QDirStat is free and does the job really good
https://github.com/jesusha123/qdirstat-macos
I’ve been using it altogether too much this last month and just bought a 4TB USB4 SSD.
And yes, codex is eating my disk, too. Ironically my solution is mostly codex - I have a task which goes around stomping on detritus.
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.
It's silly I have to tell it to make part of the build process to clean old artifacts or it'll just default to keeping endless folders of test builds and old builds without cleaning them up. The same seems to usually be true with documentation and reference material.
There was a REALLY annoying period where I'd give it full control of a VM and a dedicated project folder and it'd continually refuse to delete anything I asked it to or just silently archive it, even though everything was already in a git repo. It seems to have gotten somewhat better about that now, but I still include "create cleanup scripts to delete unnecessary project content" in the default steps before doing the final merge on a change.
Codex happily removes things I ask it to all the time. Do you have a special phrasing in agent instructions such as AGENTS.md?
1 reply →
Heh, Claude recently (last couple of weeks) left behind several jj workspaces with many GBs of builds in my env.
Had to tell it to update it's agents.md to not do that...
Codex is obsession with validation tests. It drives me insane.
That's the only reason these models are good though. They don't one shot things. They get it wrong and then keep checking until they get it right. You gotta let them test
Agents prefer some sort of tests to check their output.
3 replies →
Rust is notorious for this, one thing some people do is force Rust to have a salvage yard for builds so all those dependencies are shared by everything regardless of what you are building or where, but holy moly, can someone make Rust output smaller files? Hard drives are always having some reason to never go down to sane prices.
When I was younger I thought we would be having exabyte hard drives by now.
They present and immediately take away their own value proposition. Do AI CEOs also buy tokens, or is that the reason for human employees ?
>"One possibility is single-person startups, each with a human founder steering swarms of agents to rake in billions in revenue. Another is companies built by AI genius CEOs employing human agents only to wield pipettes and testify before Congress."
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.
Before Windows XP, desktop Windows users were accustomed to frequent system crashes. Viruses in the 1990s would take out offices around the world. Nothing collapsed, and nobody switched to Linux. Everyone was just used to it. I think most people will accept the tradeoffs, because it used to be much worse than it is now.
I meant also in terms of space and time complexity with the slower, bloatier software at every level, things would also freeze and fill up.
What people can get away with on the upper crust with end-user apps would spell disaster for the inner parts.
> desktop Windows users were accustomed to frequent system crashes
Home users maybe. I've started with Windows NT 4.0 and don't remember it being crash-prone.
2 replies →
Eh, that was said about Javascript, electron, node, etc
The world adapted, that is to say if something is popular- they will keep it going through just enough fixes to keep it going
[dead]
They've had their way since before AI was a thing and it was fine and it still is. You can spend the tokens you have on optimizing the performance of your fork of whatever software you're running. For large categories of software it's mattering less and less what other people choose to prioritize because you can choose your own priorities when you roll your own version
btw there is a storage section in Chatgpt app settings, showing used space on disk and other related stuff
I'm so glad my first move was to relegate these harnesses to docker containers.
look into ~/.bun/install/cache/@openai folder as well.
for some reason I had 11 separate codex and codex-code-mode-host binaries in mine. each weighing about ~300 MB.
Is it just me or is codex on windows slow and buggy for general work tasks? I can’t no matter what get it to control its own browser and fan spins out of control on decently new laptop. I tried Claude and it’s much better experience, got a bookkeeping workflow setup with xero mcp and reading my emails finding invoices in no time. Codex has been great for plain coding jobs though.
Prompt it to create a bash script that will clean those directories and schedule it every few minutes.
Apparently OpenAI is unable to fix this properly, even using its state of the art AI.
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...
> 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?
Because the former can be marketed very prestigiously, the latter hardly can.
According to https://www.briefia.fr/en/article/openai-revendique-la-resol... it is estimated that solving Navier-Stokes did cost OpenAI 40 million USD. I would bet that if OpenAI spent the same amount of money using its super-intelligence to fix this bug, this would work.
But seems not to be very economical. :-)
The navier Stokes work was just preparation for this finite time disk usage blowup (with smooth periodic forcing)
The term super intelligence makes me cringe so hard, you can just use the regular term.
You don't have to give any more legitimacy to Trump's inane ramblings than they already get.
Also insane ramblings too.
because they'd need to pay a real mathematician to verify the proof they claim.
Well looks like my post hit the frontpage of HN, so maybe openai will fix the bug :)
So, you’re using all of us for technical support purpose? Good to know - I wish I wouldn’t have wasted my time reading this shit.
The post is about exactly what the title says its about and also it is literally a link to a GitHub issue if you didn't want to read a big report and couldn't figure out that it was a bug report until "wasting your time" reading it and then a bunch of comments and then finally a comment saying hopefully openai will take it seriously idk what what to day
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.
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[dead]
Wow. I've tried a bunch of agent harnesses and Codex Desktop was on my list to try. It has definitely fallen off!