A detailed bug report on the OpenAI Codex CLI repository reveals that version 0.157.0 introduced a persistent background daemon (codex app-server --managed-daemon) that starts automatically when a user opens an interactive session. The daemon reparents to PID 1, surviving after every Codex window closes, and requires an explicit stop command or a full reboot to terminate. At no point does the CLI ask the user's permission. The daemon's installation procedure copies the entire platform package — roughly 374 MB including codex, codex-code-mode-host, and bundled binaries for bwrap, zsh, and rg — into ~/.codex/packages/app-server-daemon/releases/ /. This is byte-identical to what npm already installed. The result: two copies of the same software, with the daemon's copy now decoupled from whatever version the user's package manager controls. Five minutes after starting, a detached updater process (codex app-server daemon pid-update-loop) begins checking for new releases hourly. It downloads updates and restarts the backend autonomously, which can kill active work sessions after a 60-second drain budget. The updater cannot be disabled through normal configuration. When a user runs the official stop command, the updater process is not stopped — it keeps running and must be killed manually. The daemon pins the environment of whichever session happened to start it first. Environment variables like HTTPSPROXY, set per invocation in the user's wrapper, persist in the daemon and apply to all subsequent connections regardless of what later sessions specify. This creates silent proxy misrouting and makes hooks receive the daemon's working directory and terminal context rather than the session's, breaking terminal-targeting workflows. The report links six related issues on the repository, including conflicts with the Arch Linux package (#48050), npm updates leaving the app-server on stale versions while the daemon refuses recovery (#46468), and hooks that cannot identify the client terminal (#37537). The pattern is consistent: a daemon designed for a desktop app or remote-control use case was shipped as the default for a command-line tool, where the expectation is that processes live and die with their terminal. The workaround is explicit: disable the feature flag, stop the daemon, manually kill the orphaned updater, and delete the duplicated package directory. This is not a one-liner — it requires knowledge of the daemon's internal architecture to clean up. The reporter's request is modest: make daemonautostart opt-in, or at minimum, exit the daemon when its last client disconnects and stop duplicating binaries when the CLI was installed via a package manager. This is a pattern familiar from browser vendors, mobile OS updates, and enterprise SaaS: a background service that asserts control over update cadence, resource allocation, and network behavior without the user's informed consent. The difference is that Codex CLI's user base is developers — people who notice orphaned processes and 374 MB of duplicated binaries. The question is whether OpenAI treats this as a bug to fix or a platform strategy to defend.
