News for hackers. Stuff that matters.
Re:Codex CLI installs a persistent, self-updating background... by abighamb on Monday October 12, 2026 @03:26PM (#50061615)
It has pretty rapidly reached the point where I do not think any acceptable LLM-harness is widely available. Every single one I've tried has broken in bizarre ways on even minor updates.
Re:Codex CLI installs a persistent, self-updating background... by mpalmer on Monday October 12, 2026 @04:21PM (#50062452)
Pi as well? Comparatively it's quite a small surface. I haven't seen issues when I upgrade.
Re:Codex CLI installs a persistent, self-updating background... by NewJazz on Monday October 12, 2026 @04:24PM (#50062488)
Pi went searching across my entire home directory unprompted... Idk to do that without some kind of sandboxing builtin is rough and chews through tokens on things I don't really want polluting my context.
Re:Codex CLI installs a persistent, self-updating background... by ghosty141 on Monday October 12, 2026 @04:54PM (#50062945)
A coworker of mine has a pretty neat script that uses bubblewrap to wrap any application. I'm using that one too for pi and it's pretty great since you don't have to trust the harness and can quite easily customize the sandbox to your needs, e.g. disallow reading to certain directories etc.

This blogpost describes a similar thing: https://bxt.rs/blog/easy-sandboxing-on-linux-with-bubblewrap...

Re:Codex CLI installs a persistent, self-updating background... by mpalmer on Monday October 12, 2026 @04:51PM (#50062912)
Well yeah, it's YOLO-by-default by design. That's not related to upgrade churn.
Re:Codex CLI installs a persistent, self-updating background... by crossroadsguy on Tuesday October 13, 2026 @01:26AM (#50067129)
Yes, Pi as well. All these harnesses have gone off kilter and are all for the LLM, by the LLM, and of the LLM at this point.

Maybe it's like online services/tools. Use them until they are VCed and gone pivoting and then move to another tool.

Re:Codex CLI installs a persistent, self-updating background... by entropie on Monday October 12, 2026 @03:56PM (#50062074)
I used codex the first time yesterday and quickly decided I need to sandbox it and came up with a pretty easy and straightforward solution (I think).

I use nixos and use a little wrapper that wraps Codex CLI in Docker. Run codex-box /path/to/project and it starts or reuses a container with only that project bind-mounted, keeping login and history in a separate volume. It uses tmux for detaching and reattaching

https://gist.github.com/entropie/8f30b9e33e9412fda3adf2f7507...

Re:Codex CLI installs a persistent, self-updating background... by crossroadsguy on Tuesday October 13, 2026 @01:23AM (#50067105)
I was delaying it but one day Codex+GLM went ahead and did things in my ~/.dotfiles folder which I had granted only READ access for. I asked and I was given a reason which I didn't understand and didn't really want to. Right then I used sandbox-exec/safehouse (macOS) and tightened every harness installed (and the one not even installed, lest I install it later and forget to add/track them in the sb zsh init script).

But I am not satisfied. I am trying to find a really lightweight container/VM for macOS that eats very less RAM on its own and expands as needed. Because I really don't want to run an agent outside a container on my mac.

Re:Codex CLI installs a persistent, self-updating background... by entropie on Tuesday October 13, 2026 @11:22AM (#50073165)
The script is working like charm. I updated the packages so it has more access to tooling (ffmpeg, rmagick etc)
Re:Codex CLI installs a persistent, self-updating background... by natpalmer1776 on Monday October 12, 2026 @04:09PM (#50062264)
Build your own, using the broken harness

Maybe thats just the tool nerd in me that just wants the perfect tool for every job.

Re:Codex CLI installs a persistent, self-updating background... by rnxrx on Monday October 12, 2026 @05:03PM (#50063043)
Very much this... The utility of Claude has grown exponentially with the amount of work I've put into memory/context management, tooling, skills development and CLAUDE.md (and friends). I freely admit I may just be fortunate, but I've yet to hit a bug in a new release that rose above the level of minor annoyance.

The thing that really validated this point was when I recently tried Codex again. Out of the box it was OK, but not great. I swung over the memory apparatus and had it import directives from my existing Claude install and it was almost immediately quite useful in its own right and, especially, as a counterpoint to Claude when dealing with some fairly complex operational issues.