News for hackers. Stuff that matters.
Re:Codex CLI installs a persistent, self-updating background... by dingaling911 on Monday October 12, 2026 @02:44PM (#50060925)
This stuff is moving fast, should update automatically. This is kind of standard now. Browsers do it. No reason for harnesses not to do it as well.
Re:Codex CLI installs a persistent, self-updating background... by isityettime on Monday October 12, 2026 @03:05PM (#50061239)
Ordinary package managers are totally capable of updating thousands of programs without manual effort, including automatically and in the background if that's a thing you want. But they do it without violating users' sovereignty over their own computers or turning every app into a special snowflake that gets to install software (namely itself) in its own bespoke way.
Re:Codex CLI installs a persistent, self-updating background... by bayindirh on Monday October 12, 2026 @02:49PM (#50060998)
You can do this without a daemon, and without storing n previous versions as noted by another user.
Re:Codex CLI installs a persistent, self-updating background... by jmbwell on Monday October 12, 2026 @03:18PM (#50061496)
Yeah this seems like a decision yielded by a model. One of countless examples of the model’s outputs careening into individually defensible but holistically nonsensical results

A human seems less likely to embark upon a path that most humans know leads to something a human is unlikely to want

LLMs produce amazing things, but only one token at a time. Anything beyond that is retrospectively emergent at best

Re:Codex CLI installs a persistent, self-updating background... by yoyohello13 on Monday October 12, 2026 @04:15PM (#50062363)
I guarantee the prompt “add auto update feature” was the first and last human input applied to that feature.
Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @02:48PM (#50060975)
My browser doesnt update automatically, i have to approve it.

Maybe this kind of stuff is standard for some people but I absolutely loathe auto updating software for many reasons

Re:Codex CLI installs a persistent, self-updating background... by dv35z on Monday October 12, 2026 @03:17PM (#50061475)
One practical reason - system stability for important events.

I travel for work, and often have a tech demo, solution, tool, or something to show - or am running a workshop.

I usually do NOT update things right before my trip, as I want to minimize the potential for disruption.

Re:Codex CLI installs a persistent, self-updating background... by vorticalbox on Monday October 12, 2026 @03:28PM (#50061654)
Isn’t this what docker is for?

Jokes aside I do the same I tend not to upgrade my Mac, my phone unless I really have to.

The “update” button on the top of my brave install has now turned from green to orange and I’ll likely wait until it goes red

Re:Codex CLI installs a persistent, self-updating background... by TeMPOraL on Monday October 12, 2026 @03:38PM (#50061828)
> Isn’t this what docker is for?

What? Pinning a browser?

First thing it'll want to do after starting is update itself to newest version anyway.

Re:Codex CLI installs a persistent, self-updating background... by nicce on Monday October 12, 2026 @03:01PM (#50061162)
For example, Firefox updates by default and forces you to restart it, disabling using websites or seeing any site content before doing so.
Re:Codex CLI installs a persistent, self-updating background... by Zambyte on Monday October 12, 2026 @03:12PM (#50061354)
On your setup.

Firefox does not only not prompt me for updates (it only updates if I manually run an update), even if I do update with Firefox running, it does not stop me from continuing to use Firefox without restarting it. All I did was install Firefox from flathub (packaged by Mozilla (a default configuration provided by Mozilla)).

Re:Codex CLI installs a persistent, self-updating background... by nicce on Monday October 12, 2026 @03:28PM (#50061652)
I am running Firefox Developer Edition on macOS, where it is the default option. Have to set "Check for updates, but choose when to install" to get the similar behavior.
Re:Codex CLI installs a persistent, self-updating background... by djsavvy on Monday October 12, 2026 @03:05PM (#50061232)
I've been using Firefox for years and don't think I've ever seen this. Are you running some custom configuration?
Re:Codex CLI installs a persistent, self-updating background... by TeMPOraL on Monday October 12, 2026 @03:40PM (#50061868)
Standard on Linux, I believe. One of many reasons I got back to Windows as my main OS (with Linux needs fulfilled by WSL).
Re:Codex CLI installs a persistent, self-updating background... by farlight on Monday October 12, 2026 @05:30PM (#50063312)
Re:Codex CLI installs a persistent, self-updating background... by nicce on Monday October 12, 2026 @03:28PM (#50061657)
Firefox Developer Edition on macOS.
Re:Codex CLI installs a persistent, self-updating background... by djsavvy on Monday October 12, 2026 @06:46PM (#50064136)
that's exactly my setup as well! strange
Re:Codex CLI installs a persistent, self-updating background... by RobotToaster on Monday October 12, 2026 @03:13PM (#50061386)
I've never seen that behaviour, it downloads updates in the background and then gives me a little notification that I should restart it to update, but it's dismiss-able.
Re:Codex CLI installs a persistent, self-updating background... by nicce on Monday October 12, 2026 @03:29PM (#50061671)
I think this is the old default option. What options you see in the update options?
Re:Codex CLI installs a persistent, self-updating background... by six_seven on Monday October 12, 2026 @03:26PM (#50061619)
Are you sure this isn't your organization's update policy kicking in here?
Re:Codex CLI installs a persistent, self-updating background... by 4chandaily on Monday October 12, 2026 @03:13PM (#50061369)
Iirc, this is a pattern of the flatpack version of Firefox. I do not believe the .deb does this.
Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @08:27PM (#50064971)
Not on my machine
Re:Codex CLI installs a persistent, self-updating background... by rootnod3 on Monday October 12, 2026 @11:24PM (#50066233)
Unless I rebuild my ports, Firefox does fuck all to my system. If it ever did, I would nuke it immediately.
Re:Codex CLI installs a persistent, self-updating background... by jstummbillig on Monday October 12, 2026 @03:07PM (#50061260)
Being able to turn auto-updates off is okay, but that being the default would certainly not be okay in Codex, giving the reach, what it can do and how immature it is.
Re:Codex CLI installs a persistent, self-updating background... by judge2020 on Monday October 12, 2026 @06:16PM (#50063838)
> My browser doesnt update automatically, i have to approve it.

Have you ever actually blocked it due to something in the new version, or is it mostly to control the timing of when it updates?

Re:Codex CLI installs a persistent, self-updating background... by icantevenhold on Monday October 12, 2026 @08:27PM (#50064969)
Only to control the timing
Re:Codex CLI installs a persistent, self-updating background... by wtallis on Monday October 12, 2026 @03:06PM (#50061252)
Serious tools shouldn't do this. Sure, you can offer an opt-in rapid release beta update option, but if you can't go more than a month without forcing me into a "stable" update that changes the UI and behavior I'm getting used to, then I'm not going to consider your software stable and reliable enough to be worth developing expertise in using.
Re:Codex CLI installs a persistent, self-updating background... by dingaling911 on Monday October 12, 2026 @04:16PM (#50062365)
The entire class of software (harnesses) you're talking about was literally invented like 2 years ago...
Re:Codex CLI installs a persistent, self-updating background... by wtallis on Monday October 12, 2026 @10:25PM (#50065808)
I don't see how that excuses anything. It certainly doesn't give harness developers an excuse to be disrespectful to their users. It shouldn't give harness developers any reason to not even try to produce a stable release with a well-designed UI instead of a janky mess that gains new bugs every time you try to use it.

There are contexts where "move fast and break things" can make sense, but usually not when it's other people's workflows that you're breaking.

Just how old do you think a category of software product needs to be before it's reasonable for users to start expecting professionalism from the developers?

Re:Codex CLI installs a persistent, self-updating background... by dingaling911 on Monday October 12, 2026 @11:28PM (#50066261)
The majority of harness users are the equivalent of boomers using browsers. They don't really care.
Re:Codex CLI installs a persistent, self-updating background... by wren6991 on Monday October 12, 2026 @02:49PM (#50060989)
If software engineering is solved they should be able to get it right the first time
Re:Codex CLI installs a persistent, self-updating background... by Yizahi on Monday October 12, 2026 @03:48PM (#50061971)
Software Engineering clearly is solved, that's why Google has a tiny animated banner on the AI Studio sidebar (advertising subscription upgrade), which shows a simple animated border around it and utilizing exactly 100% of the GPU to render just that banner. And there is a browser extension removing that styling element (without banner GPU load is obviously under 0.1% as it should be) released way back in May. So the almighty AI didn't manage to fix a major UI blocker for a flagship AI product in half a year now. :)
Re:Codex CLI installs a persistent, self-updating background... by wren6991 on Monday October 12, 2026 @03:53PM (#50062040)
When I had a Claude account (cancelled ~May time) I vividly remember the web chat having broken editing for backtick-quoted monospace text. If you typed <space>`foobar`<space> the last space would move the cursor backward into the closing quote, and the space would be emitted inside the monospaced region. It was like this for several months (on Firefox). I always found this baffling for a product marketed to programmers.
Re:Codex CLI installs a persistent, self-updating background... by whythismatters on Monday October 12, 2026 @04:39PM (#50062733)
Same with their desktop app by the way, absolutely infuriating.
Re:Codex CLI installs a persistent, self-updating background... by rurban on Tuesday October 13, 2026 @02:11AM (#50067474)
You don't understand Google business. It's an ad company, not a tech company. Nobody cares about that banner.
Re:Codex CLI installs a persistent, self-updating background... by phoghed on Monday October 12, 2026 @03:29PM (#50061672)
Coding is solved, software engineering still TBD
Re:Codex CLI installs a persistent, self-updating background... by dingaling911 on Monday October 12, 2026 @02:50PM (#50061015)
CODEX WRITES ITSELF! DONT YOU PEOPLE UNDERSTAND!!!!!
Re:Codex CLI installs a persistent, self-updating background... by TeMPOraL on Monday October 12, 2026 @03:41PM (#50061878)
Nah, you're confusing it with Autolith.
Re:Codex CLI installs a persistent, self-updating background... by bayindirh on Monday October 12, 2026 @02:51PM (#50061037)
So you imply that Codex has a hoarding issue?
Re:Codex CLI installs a persistent, self-updating background... by Rapzid on Monday October 12, 2026 @03:33PM (#50061757)
It loves hording issues. Over 15 THOUSAND on GH.
Re:Codex CLI installs a persistent, self-updating background... by jonplackett on Monday October 12, 2026 @02:58PM (#50061134)
It gets very attached to itself
Re:Codex CLI installs a persistent, self-updating background... by swatcoder on Monday October 12, 2026 @02:58PM (#50061120)
Products moving fast doesn't mean that they're moving in the direction I want, or that I want them to move underneath me while I'm in the middle of a project.

Auto-update systems have value but are not a suitable default for professional tools.

Re:Codex CLI installs a persistent, self-updating background... by RobotToaster on Monday October 12, 2026 @03:11PM (#50061342)
Then use the package manager, or windows store on windows.
Re:Codex CLI installs a persistent, self-updating background... by johnnyApplePRNG on Monday October 12, 2026 @02:48PM (#50060982)
Sure yea just let sam altman install a rootkit on your box.

That's not odd whatsoever. /s

Re:Codex CLI installs a persistent, self-updating background... by dingaling911 on Monday October 12, 2026 @02:50PM (#50061007)
you run it on the bare metal?!! Balls. I run it in a container
Re:Codex CLI installs a persistent, self-updating background... by crossroadsguy on Monday October 12, 2026 @11:56PM (#50066475)
Only if OSes have some easy and sanenly robust way of limiting app access in such a granular way that these apps might be as well forced to start behaving.

Like a simple:

- Dropbox:

    - Asked Permissions: File Access [{~/Dropbox, rw}]; App Install/Exec [/Applications/Dropbox.app]; Internet Access [*.dropbox.com]

    - They can have additional system defined accessible path inside ~/.cache, ~/.config etc and accessible only via their app package names (if they change their signature - not notarised or shit, user gets a notification and approves it) -> this is the tricky part. I'd rather have an app get a ~/.local/appdata/<app/package name> sort of blanket access for anciliary things and do whatever the shit you want do there.

    - optional permissions: []

 and so on… 
(also: the example given above is not fair game for nitpicking :D)

The thing is: the Internet access part one can control with Lulu or other similar apps. But anything else is a user nightmare - next to impossible even for a cli/tweaking/etc comfortable user. And mac's TCC is a royal mess - even their UI part for this is utterly confusing. I think only the Linux world can achieve something sane+easy like this (if it doesn't have that already; though they have not been known for being "easy").

I have achieved a lot of these for harnesses using sandbox-exec (by basically doing: "deny *; then selectively allow") on mac but it was a pain and I can't even think of trying something like that for "normal" apps.