• Sources: primary, discussion
  • Summary: The issue was opened on 2026-09-25 against CLI 0.157.0, it is open, and it is reproduced on Linux, WSL2 and Windows, with codex features disable daemon_auto_start given as the reporter's workaround. Whether the behaviour is still the default on the current release line is unverified here, because the thread references later releases up to 0.160.1 without restating the default. Since CLI 0.157.0, opening an interactive codex session starts codex app-server --managed-daemon in its own session with no TTY, reparented to PID 1, and it survives closing every Codex window until an explicit daemon stop or a reboot. The CLI copies about 374 MB of platform package, including bundled bwrap, zsh and rg, into ~/.codex/packages/app-server-daemon/releases/ and runs the daemon from that copy, then a detached pid-update-loop process checks for updates five minutes after start and hourly after that, downloading releases and restarting the backend. The daemon also pins the environment of whichever session started it, so a per-invocation HTTPS_PROXY setting leaks into later sessions, and daemon stop leaves the updater running.
  • Why it matters: The serving backend's version decouples from the binary the package manager installed, so a machine's effective Codex version is set by a background updater rather than by the fleet's package policy.
  • Follow-up: Whether the default changes and whether daemon stop also stops the update loop.