News for hackers. Stuff that matters.
Re:Codex CLI installs a persistent, self-updating background... by InsideOutSanta on Monday October 12, 2026 @02:57PM (#50061105)
All of the harnesses I've used are terrible at cleaning up after themselves. They leave all kind of clutter behind, to the point where on my dev VM, I now have an LLM run once a day to just look through the disk and delete everything that looks like it's leftover garbage.

It's like fighting fire by employing an arsonist.

Re:Codex CLI installs a persistent, self-updating background... by sroussey on Monday October 12, 2026 @03:10PM (#50061316)
I just erased 20GB of Cursor’s cruft.
Re:Codex CLI installs a persistent, self-updating background... by TeMPOraL on Monday October 12, 2026 @03:28PM (#50061660)
Is that cruft or past conversation history / subagent history and observability logs?
Re:Codex CLI installs a persistent, self-updating background... by InsideOutSanta on Monday October 12, 2026 @03:48PM (#50061976)
Just garbage. Temp files, worktrees that weren't removed after subagents finished, build files... all kinds of things.
Re:Codex CLI installs a persistent, self-updating background... by thdr on Monday October 12, 2026 @03:55PM (#50062069)
But that's agent behavior, and not harness responsibility...?
Re:Codex CLI installs a persistent, self-updating background... by klodolph on Monday October 12, 2026 @06:46PM (#50064134)
Harnesses should be responsible IMO for managing lifecycle stuff, including worktrees and temp files.

It’s simple, deterministic stuff. At least most of the time.

Re:Codex CLI installs a persistent, self-updating background... by TeMPOraL on Tuesday October 13, 2026 @06:07PM (#50079576)
Hence my question.

I assume auto-updates are handled by deterministic code that's far away from anything agents can touch (self-modifying harnesses like Autolith notwithstanding). With the same behavior showing up in multiple high-profile harnesses (Codex, Claude Code), it feels likely there must be some actual reason for doing it this way.

Re:Codex CLI installs a persistent, self-updating background... by klodolph on Friday October 16, 2026 @01:15PM (#50121289)
I didn’t see your reply.

It should be the harness responsibility to create / destroy things like worktrees and scratch spaces, and communicate to the agent (e.g. via system prompt) where the scratch space is and its purge schedule. Harness should also set appropriate env vars to make this work in tools.

> With the same behavior showing up in multiple high-profile harnesses (Codex, Claude Code), it feels likely there must be some actual reason for doing it this way.

I think fixing it is just not high on the priority list.

Re:Codex CLI installs a persistent, self-updating background... by agentdev001 on Monday October 12, 2026 @03:15PM (#50061412)
Harness problem, or model problem?
Re:Codex CLI installs a persistent, self-updating background... by corndoge on Monday October 12, 2026 @03:29PM (#50061677)
Let's be real, what do you think wrote the harness?
Re:Codex CLI installs a persistent, self-updating background... by NooneAtAll3 on Monday October 12, 2026 @03:40PM (#50061866)
> I now have an LLM run once a day to just look through the disk and delete everything that looks like it's leftover garbage

...are you sure it wouldn't consider your personal files garbage?

Re:Codex CLI installs a persistent, self-updating background... by InsideOutSanta on Monday October 12, 2026 @03:46PM (#50061953)
"In my dev VM". Everything of value in there is in a git repo.
Re:Codex CLI installs a persistent, self-updating background... by judge2020 on Monday October 12, 2026 @06:09PM (#50063762)
Installed "clor.com" and it got into a loop of downloading its docker image from ghcr them throwing it away immediately because it was supposedly out of date (iirc). 65mbps continuous transfers for a week until I looked at my network traffic and saw 500gb of rx per day.
Re:Codex CLI installs a persistent, self-updating background... by s3p on Monday October 12, 2026 @09:21PM (#50065368)
Sisyphus' updater
Re:Codex CLI installs a persistent, self-updating background... by klodolph on Monday October 12, 2026 @06:45PM (#50064128)
Over eager use of /tmp is the worst. That’s RAM, my boy! Precious gold.
Re:Codex CLI installs a persistent, self-updating background... by arcanemachiner on Monday October 12, 2026 @07:37PM (#50064556)
I don't think that's always true.

Although I just looked into it, and even Ubuntu 26.04 appear to default to tmpfs for /tmp storage, so I guess it's fairly universal now.

Not sure if I agree with that idea in principle... What's wrong with just wiping it intermittently??

Re:Codex CLI installs a persistent, self-updating background... by trollbridge on Monday October 12, 2026 @09:23PM (#50065392)
It’s RAM unless you have swap enabled.
Re:Codex CLI installs a persistent, self-updating background... by matltc on Tuesday October 13, 2026 @01:06AM (#50066982)
Did not know this. Was looking at htop yesterday scratching my head as to why there was over a GB in swap with ram <0.25 capacity. Had been teeing logs there pretty heavily
Re:Codex CLI installs a persistent, self-updating background... by cstever on Monday October 12, 2026 @08:21PM (#50064927)
Running an LLM to delete files seems like overkill to me. Couldn't a cron job do the same thing? Or is the clutter just put into random places, which, if true, seems like bad software, which then leads me to consider the output of LLMs in general, which then leads me to wonder why are we doing this?

But, I'm just wondering.

Re:Codex CLI installs a persistent, self-updating background... by dannyw on Monday October 12, 2026 @09:06PM (#50065255)
Oh it makes all sorts of temporary files and directories, sometimes in the right places as per UNIX filesystem conventions, but often not.
Re:Codex CLI installs a persistent, self-updating background... by hiitsmyaccount on Monday October 12, 2026 @10:31PM (#50065852)
You could use snapshots or whatnot to reset the state whenever you like. Using an LLM to clean up files often seems like overkill to me.
Re:Codex CLI installs a persistent, self-updating background... by ipaddr on Tuesday October 13, 2026 @12:58AM (#50066926)
Wouldn't a snapshot delete everything else you saved?
Re:Codex CLI installs a persistent, self-updating background... by groby_b on Tuesday October 13, 2026 @02:22AM (#50067542)
You keep your source tree on a separate file system with version control, one hopes.

So you only snapshot the rest. (And since your source tree is under version control, finding stray garbage there is straightforward unless you checked it in)

Re:Codex CLI installs a persistent, self-updating background... by noosphr on Monday October 12, 2026 @11:09PM (#50066112)
Just have an emphemal VM which you nume daily.

Its the only way I trust to install anything from these companies.

Re:Codex CLI installs a persistent, self-updating background... by rurban on Tuesday October 13, 2026 @01:31AM (#50067162)
Went down the same hole, seeing all the massive logs, in plain text and as json, but ever eventually found the real culprit: snap caches of insane sizes.
Re:Codex CLI installs a persistent, self-updating background... by clickety_clack on Tuesday October 13, 2026 @09:08AM (#50071116)
Why wouldn’t you just rebuild the VM every day? Then you don’t have to run around trying to catch and delete things, it’s set up with exactly what you want.
Re:Codex CLI installs a persistent, self-updating background... by InsideOutSanta on Tuesday October 13, 2026 @11:49AM (#50073632)
It's funny how differently people use LLMs. I have agents that run for weeks, building something from a detailed plan with clear goals that gate progress. I don't like to constantly baby LLMs and tell them what to do. It would be inconvenient to rebuild the VM every day, then restore it and start everything again.
Re:Codex CLI installs a persistent, self-updating background... by clickety_clack on Tuesday October 13, 2026 @02:04PM (#50075970)
When did you create that workflow? I ask because I used to have something with a lot of carefully designed stuff like that back in Spring, but as the Summer progressed I found that getting out of the agent's way more and more has worked really well. I've been coding for 17 years, so this year has been a real journey as I've let go of some of the control of "this is how each step must be done". Those years of experience do mean that problems jump out pretty readily after the fact and and once you point out the problems to the agent it's pretty good at correcting them.

Today, I generally spend a few hours on a spec, let the agent run for 4 to 6 hours and I'm 90% there, with maybe a couple of days of tweaks, then a couple of days of iterations coming from user feedback after that. I've stopped using skills almost entirely now, mainly using them just to keep discovery of MCP or API docs out of context until needed. I have a few bullet points on testing and style in AGENTS.md, but I'm pretty sure it would probably run pretty close to what I'm looking for even without those these days.