Codex CLI installs a persistent, self-updating background daemon by default

Re:Codex CLI installs a persistent, self-updating background... by silverbluep on Monday October 12, 2026 @04:17PM (#50062392)

Codex is very badly structured. I was an early user with codex. But it mixes state and configuration data; which is why I can't really declaratively manage it in my nix-darwin environment; so abandoned it a while ago. This issue being raised, and the way that the codex development responds back to it makes me not trust their harness ever again. I only use codex in opencode; which seems to be doing OK. At least openai doesn't gate their product to their harness like anthropic.

Not trying to sing praises; i think opencode is doing a bunch of weird stuff too but it's not codex level.

[ Parent | on HN ]

Re:Codex CLI installs a persistent, self-updating background... by dizhn on Monday October 12, 2026 @08:26PM (#50064964)

Antigravity's agy is the same. I suspect ACP and GUI too. It has no env var or parameter to set its config dir. You can set home but that also set's agent's home. How big of a piece of crap it is is literally hard to fathom.

It doesn't even have a place to check your remaining time or limits except for an in app /quota command that the CLI does not expose.

[ Parent | on HN ]

Re:Codex CLI installs a persistent, self-updating background... by llelouch on Tuesday October 13, 2026 @01:38PM (#50075582)

>At least openai doesn't gate their product to their harness like anthropic.

Ant doesn't do this. (Anymore)

[ Parent | on HN ]