News for hackers. Stuff that matters.
Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @02:45PM (#50060934)
It also fills up my HD with old versions. I investigated and it took up something like 12 gigabytes in total on my system; which seems insane to me, it’s just a harness?

People moan about how badly made Claude code is but Codex seems much worse on every metric

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.

Re:Codex CLI installs a persistent, self-updating background... by umvi on Monday October 12, 2026 @02:54PM (#50061066)
Can't wait until we get really well designed harnesses written in a compiled language that doesn't bloat my computer. Will probably have to be written by a company other than OpenAI because codex is like the exact opposite of everything I just listed
Re:Codex CLI installs a persistent, self-updating background... by dummydummy1234 on Monday October 12, 2026 @02:56PM (#50061100)
Codex is written in rust, fyi... Not that I disagree.
Re:Codex CLI installs a persistent, self-updating background... by umvi on Monday October 12, 2026 @03:01PM (#50061165)
Oh, I haven't been keeping up. I assumed it was still TS since it prompts me to run npm all the time.
Re:Codex CLI installs a persistent, self-updating background... by Twirrim on Monday October 12, 2026 @03:45PM (#50061933)
They just use npm as a binary delivery mechanism, for whatever reason (I guess they expect all their users to have npm?)
Re:Codex CLI installs a persistent, self-updating background... by judge2020 on Monday October 12, 2026 @06:13PM (#50063801)
It's pretty darn ubiquitous, yeah. Plus enterprises tend to run npm mirrors, so delivery integrates into existing IT compliance frameworks.
Re:Codex CLI installs a persistent, self-updating background... by lynx97 on Monday October 12, 2026 @03:05PM (#50061235)
Which generates unnecessarily huge binaries.
Re:Codex CLI installs a persistent, self-updating background... by rfgplk on Monday October 12, 2026 @03:08PM (#50061277)
It's because they statically linked it, and probably rely on a trillion pointless crates (as is standard in Rust development). A good statically linked harness can easily be ~5MB MAX
Re:Codex CLI installs a persistent, self-updating background... by cedws on Monday October 12, 2026 @10:05PM (#50065680)
5MB is still huge.
Re:Codex CLI installs a persistent, self-updating background... by smartmic on Monday October 12, 2026 @03:16PM (#50061457)
Found this one: https://usehax.dev/

Anyone experiences with it?

Re:Codex CLI installs a persistent, self-updating background... by serf on Monday October 12, 2026 @03:44PM (#50061918)
it's okay.

it's minimal and somewhat opinionated, not integrated well with memory subsystems (although that's kind of the point)

my only real criticism is that last I played with it it deals with slow provider responses very poorly , so lots of locally hosted llms require a lot of tuning to get it to handle streaming/non-streaming/timers well.

way less minimal (but still pretty minimal) I prefer Pi; but different markets I think.

hax fit my openbsd laptop well, espescially since Pi and related derivatives are kind of un-spokenly incompatible with the BSDs.

Re:Codex CLI installs a persistent, self-updating background... by OleksandrC on Monday October 12, 2026 @03:58PM (#50062115)
(author passing by) Could you please report the issues you've experienced on the repo? I did quite a bit of testing myself on local models (Qwen, Ornith, Gemma, Muse Glimmer) with llama.cpp, and they all worked fine. Details would be helpful.

Also one brief note for Codex users specifically. hax can work out-of-the-box as codex-cli drop-in replacement (since it can use the already authenticated codex token), so it's super easy to try it - basically it will be a zero-config experience.

Re:Codex CLI installs a persistent, self-updating background... by imrehg on Monday October 12, 2026 @09:23PM (#50065390)
Thanks for making it :)
Re:Codex CLI installs a persistent, self-updating background... by seanhunter on Tuesday October 13, 2026 @10:18AM (#50072180)
Firstly thanks for writing it and making it available. The problem I had when I tried it is it would consistently blow out the small context window of my local qwen and although there was seemingly a config knob I could use to prevent that, seemingly that didn’t do anything.
Re:Codex CLI installs a persistent, self-updating background... by imrehg on Monday October 12, 2026 @09:22PM (#50065382)
Yeah, using it a bunch with local LLMs. It's fast (small system prompt), focused on the basics, made around simple choices, and possibility to call it in scripts.

So far I have very positive experiences, the results are generally better (and not just faster) than in other harnesses with the same models. I've done the same (user) prompts for tasks in a range of them, and compare the outcome to eval between them. Simple (harness) beats complicated one many times. I do wish it could use MCP though, but not as often as I think, and CLI tool usage often compensates on this front with little extra effort)

That is now my usuall go-to harness for things usually. Still figuring out the edges though (when we get off the happy path, like models reaching their max context, or such...)

It's very light, recommed you try it out, and see if it fits your toolbox.

Re:Codex CLI installs a persistent, self-updating background... by crossroadsguy on Monday October 12, 2026 @10:15PM (#50065765)
That landing page is hard to look at, let alone read. Have LLMs really not yet learned to write webpages that read the sytem theme and look that way? Must be hard.
Re:Codex CLI installs a persistent, self-updating background... by freakynit on Monday October 12, 2026 @10:22PM (#50065790)
Just tried. And wow!! I opened my mac's activity monitor to see how much load it was putting on my system, and i had to scroll all the way down ... unlike those current harnesses that sit right on top (sorted by used cpu, descending).

And it worked. I'm switching to this unless i find a reason not to.

Re:Codex CLI installs a persistent, self-updating background... by koe123 on Monday October 12, 2026 @03:16PM (#50061448)
Omp
Re:Codex CLI installs a persistent, self-updating background... by rfgplk on Monday October 12, 2026 @03:01PM (#50061176)
Just write your own harness. Ironically Codex/Claude are both abysmal.
Re:Codex CLI installs a persistent, self-updating background... by sroussey on Monday October 12, 2026 @03:15PM (#50061434)
I did, and the weird things you have to do to make work at least decent. I’ve been doing evals and I got some things better than opencode but not as good as pi. Though my goal is to optimize for a browser and browser based llm so it can create stuff in a web container or at least generate ui by requesting json schema (a2ui style).
Re:Codex CLI installs a persistent, self-updating background... by theowaway213456 on Monday October 12, 2026 @03:12PM (#50061347)
How do you even write a harness that can use a Claude subscription? I thought it was not allowed by Anthropic's ToS and can get you banned?
Re:Codex CLI installs a persistent, self-updating background... by rfgplk on Monday October 12, 2026 @03:55PM (#50062072)
If you're using the sub, only OpenAI (via the OAuth token) is viable. Claude is API_KEY only
Re:Codex CLI installs a persistent, self-updating background... by sroussey on Monday October 12, 2026 @03:16PM (#50061454)
That’s a different discussion.
Re:Codex CLI installs a persistent, self-updating background... by fasterik on Monday October 12, 2026 @03:34PM (#50061764)
I suspect a lot of people wouldn't use AI if they had to pay per token at current rates. Yes, it's technically a different discussion, but "just write your own harness" isn't really an answer for the vast majority of us riding on the investor-subsidized subscription plans.
Re:Codex CLI installs a persistent, self-updating background... by agentdev001 on Monday October 12, 2026 @03:17PM (#50061461)
It's allowed, but you get bumped to per token pricing.
Re:Codex CLI installs a persistent, self-updating background... by bhelkey on Monday October 12, 2026 @03:38PM (#50061834)
That defeats the purpose of using the Claude subscription.
Re:Codex CLI installs a persistent, self-updating background... by arcanemachiner on Monday October 12, 2026 @07:39PM (#50064570)
Not true; They rolled back some of the changes you're thinking about IIRC.
Re:Codex CLI installs a persistent, self-updating background... by colinmarc on Monday October 12, 2026 @05:30PM (#50063320)
It's trivial to bypass this by tweaking the system prompt in other harnesses. They use string matching and a blacklist.

https://x.com/FlorianKluge/status/2041855675295318039

(Whether that's against the ToS is not clear.)

Re:Codex CLI installs a persistent, self-updating background... by pugz on Monday October 12, 2026 @06:43PM (#50064110)
Amp recently achieved it. Apparently it's permitted as long as you use the Claude Agent SDK. https://ampcode.com/news/use-your-claude-plan
Re:Codex CLI installs a persistent, self-updating background... by reacharavindh on Tuesday October 13, 2026 @06:33AM (#50069544)
This is bait and switch..

You can’t just use your Claude sub on a third party harness without getting blocked even if you use the Agent SDK. Apparently, Anthropic gives “credits” depending on your sub and you can use those _credits_ when you use third party harnesses or Claude -p mode. That usage is not the same Claude sub one would assume it is… It is all quite deceiving. Don’t get a Claude sub unless you’re okay with being locked into Claude Code…

Re:Codex CLI installs a persistent, self-updating background... by _flux on Monday October 12, 2026 @11:49PM (#50066411)
I don't use Claude, but it appears it is permitted to use Claude as a stdin/stdout -communicated tool using JSON, or use Claude SDK, with the monthly plans. Monthly Max/Team plans also include credits that could be used directly via the API: https://support.claude.com/en/articles/17154008-monthly-api-... .

E.g. OpenCode can be used with all three methods. Looks like it needs a plugin for the two Claude methods, though.

Re:Codex CLI installs a persistent, self-updating background... by joquarky on Monday October 12, 2026 @06:34PM (#50064025)
They're not made of fairy dust; you can build your own.
Re:Codex CLI installs a persistent, self-updating background... by elcritch on Tuesday October 13, 2026 @01:01AM (#50066941)
There's https://3code.capocasa.dev/ which is written in Nim and focuses on token efficiency.
Re:Codex CLI installs a persistent, self-updating background... by akho on Tuesday October 13, 2026 @10:56AM (#50072744)
does it achieve token efficiency? vs something like maki? It's not at all clear what the method of that "efficiency" is.

my main issues with maki are that the line editor (what you use to enter your prompts) is very barebones, copy-paste is broken (no middle-click paste, or copy to PRIMARY; implicit copying to CLIPBOARD that can only be used with a mouse), and scrollback is not native. So it's not a real cli, but some sort of weblike tui.

I tried 3code; it does not mess with selection, but code printed in the conversation has | markers in every line, and is thus uncopyable in practice. Don't know how to use that.

Re:Codex CLI installs a persistent, self-updating background... by elcritch on Tuesday October 13, 2026 @07:30PM (#50080421)
I've only dabbled with 3code. The author of 3code is pretty active, so he may take suggestions. I'd agree that copy/paste is important for a good agent workflow.
Re:Codex CLI installs a persistent, self-updating background... by warpspin on Tuesday October 13, 2026 @01:27PM (#50075409)
Thanks for that. Looks like exactly the agent I might have been looking for.
Re:Codex CLI installs a persistent, self-updating background... by nicce on Monday October 12, 2026 @02:58PM (#50061136)
> People moan about how badly made Claude code is but Codex seems much worse on every metric

Also, it feels that chatgpt.com and aistudio.google.com are the buggiest websites I have seen for long time. Why it is always something related to LLMs?

Re:Codex CLI installs a persistent, self-updating background... by sdcfgy on Monday October 12, 2026 @03:13PM (#50061374)
All the LLM turds we've curled out at work are the same.
Re:Codex CLI installs a persistent, self-updating background... by demibabs on Monday October 12, 2026 @03:50PM (#50062007)
It’s actually insane how buggy the Gemini web version is (or at least was a few months ago, since I stopped using it).
Re:Codex CLI installs a persistent, self-updating background... by novafunc on Monday October 12, 2026 @08:20PM (#50064912)
It's improved. The scrolling used to be terribly glitchy and would make it difficult to read as text was generated.

But in the same fix, they also removed the reasoning-sample, which kinda sucked.

Re:Codex CLI installs a persistent, self-updating background... by platevoltage on Monday October 12, 2026 @03:59PM (#50062126)
ChatGPT.com is dreadful. The whole thing chokes when the conversation gets moderately long. It's amazing that it's been allowed to stay this way.
Re:Codex CLI installs a persistent, self-updating background... by dannyw on Monday October 12, 2026 @09:09PM (#50065283)
I suspect it’s intentional.

Chat sessions are not metered by token usage but rather a fairly high limit of messages per day or something.

The longer chats you have, the more context and token input. So I think that discourages longer chats, and encourages users to start new chats.

Re:Codex CLI installs a persistent, self-updating background... by bakugo on Monday October 12, 2026 @03:12PM (#50061352)
Because they're the most likely to be 100% vibe coded. And as much as some people still deny it, AI code = buggy code.
Re:Codex CLI installs a persistent, self-updating background... by stravant on Tuesday October 13, 2026 @05:55AM (#50069206)
Because LLMs are changing so fast that nobody wants to spend time carefully engineering an efficient setup for them which might just get thrown away in 6 months when the modality changes again.
Re:Codex CLI installs a persistent, self-updating background... by steve1977 on Tuesday October 13, 2026 @10:51AM (#50072669)
But are we not told that LLMs are so powerful that nobody would need to spend time to engineer that?
Re:Codex CLI installs a persistent, self-updating background... by whimblepop on Monday October 12, 2026 @03:39PM (#50061850)
My preferred Nix package for this patches at least that behavior out, afaict: https://github.com/numtide/llm-agents.nix/blob/dc285bfd94ec7...

https://github.com/numtide/llm-agents.nix/

Re:Codex CLI installs a persistent, self-updating background... by jonplackett on Monday October 12, 2026 @02:58PM (#50061123)
It’s extremely ironic that the software that’s meant to end software is itself pretty terrible software.
Re:Codex CLI installs a persistent, self-updating background... by AgharaShyam on Monday October 12, 2026 @03:24PM (#50061593)
for some reason I had 11 separate codex and codex-code-mode-host binaries in my ~/.bun/install/cache/@openai . each weighing about ~300 MB. might be worth a look to anyone running low on disk space.
Re:Codex CLI installs a persistent, self-updating background... by charliermarsh on Monday October 12, 2026 @03:22PM (#50061555)
I haven't worked with the update subsystem before but that seems like an oversight to me. I'm gonna fix it.
Re:Codex CLI installs a persistent, self-updating background... by orliesaurus on Monday October 12, 2026 @03:51PM (#50062010)
what's the lazy way to check? can you share where/how you cleaned up?
Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @08:31PM (#50064993)
I just asked Claude where all my disk space went and it gave me a really useful breakdown; turns out i had some unused local models in random folders ~200gb worth. Plus aforementioned harness bloat plus 100gb of unused npm stuff etc
Re:Codex CLI installs a persistent, self-updating background... by rfgplk on Monday October 12, 2026 @02:58PM (#50061130)
Yep, .codex/packages/standalone/releases keeps all the old versions. Also each codex bin is somehow ~300MB.
Re:Codex CLI installs a persistent, self-updating background... by JodieBenitez on Monday October 12, 2026 @03:04PM (#50061222)
thanks, I just removed all the old stuff.
Re:Codex CLI installs a persistent, self-updating background... by bayindirh on Monday October 12, 2026 @02:49PM (#50060991)
Remember: VSCode runs a complete headless Eclipse instance as its Java LSP, so I don't expect quality code from any of the big companies anymore.
Re:Codex CLI installs a persistent, self-updating background... by dwattttt on Monday October 12, 2026 @03:06PM (#50061244)
Are you referring to something built into VS Code, or an extension? It looks you're talking about https://github.com/redhat-developer/vscode-java, which is RedHat's doing.
Re:Codex CLI installs a persistent, self-updating background... by accrual on Monday October 12, 2026 @03:06PM (#50061251)
Yes, my DEV VM tended to fill up with VSCode backups as well. I finally expanded the disk so it's less of an issue today, but for a while ENOSPC was resolved by cleaning up ~/.vscode-server/cli/servers.
Re:Codex CLI installs a persistent, self-updating background... by Onavo on Monday October 12, 2026 @02:52PM (#50061049)
Even if you installed codex with brew?
Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @08:32PM (#50064999)
Not sure I installed it via some random install.sh which they promoted
Re:Codex CLI installs a persistent, self-updating background... by verdverm on Monday October 12, 2026 @07:39PM (#50064569)
Don't get me started on my custom NES harness, it generates ~10MB per turn. At least the harness itself is pretty tiny
Re:Codex CLI installs a persistent, self-updating background... by wodenokoto on Tuesday October 13, 2026 @01:19AM (#50067085)
I mean, they are the premier showcase of vibe coding - can we really expect anything but the finest soup of slop?
Re:Codex CLI installs a persistent, self-updating background... by srigi on Tuesday October 13, 2026 @02:17AM (#50067516)
Recently they broke the most essential thing you can do in TUI - copying the text selected with the mouse: https://github.com/openai/codex/issues/48125