Codex CLI silently installs a self-updating background daemon on every launch
Codex CLI installs a persistent, self-updating background daemon by default
Since version 0.157.0, opening an interactive Codex CLI session spawns a persistent background daemon that survives after every window closes, copies a 374 MB platform package into ~/.codex, and runs an hourly self-updater that can kill active turns. It also pins the proxy environment of whichever session started it. Users want daemon_auto_start to be opt-in, not the default.
For a CLI, the least surprising default is that the backend lives and dies with the window, runs the binary I installed, and doesn't update itself in the background.