TL;DR
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
A user report for Codex CLI 0.157.0 says opening an interactive session starts a persistent background app-server daemon that can update itself independently of the installed CLI. The report describes behavior on Linux under WSL2; OpenAI’s response and whether the default applies across platforms or installation methods are not included in the source material.
A user of Codex CLI 0.157.0 says that opening an interactive session on Linux under WSL2 starts a persistent background app-server daemon, which can download updates and restart independently of the CLI package. The report, filed on GitHub, asks for automatic startup to be opt-in and describes effects on version control, session behavior and process cleanup; it does not establish how broadly the behavior applies or include an OpenAI response.
According to the report, launching the CLI starts codex app-server –managed-daemon in a detached session. It remains running after the Codex window closes, until explicitly stopped or the system reboots. The user says the process copies a platform package of about 374 MB into ~/.codex/packages/app-server-daemon/releases/ and runs the backend from that copy rather than directly from the npm-installed files.
The reporter also says a separate pid-update-loop process checks for updates five minutes after startup and hourly thereafter, then downloads releases and restarts the backend. That account cites a related issue describing a 60-second drain budget before active turns may be force-stopped. These are details from the user’s report and linked issue, not independently verified findings in the material provided.
The issue describes other possible effects: the daemon retains environment variables from the session that started it, including a configured HTTPS_PROXY; remote-mode hooks may receive the daemon’s working directory instead of a session’s; and terminal-targeting hooks may not identify the client terminal. The reporter says codex app-server daemon stop stopped the server but left the updater running in their test.
Updates Can Outlive CLI Sessions
If the reported behavior is representative, the distinction between installing Codex CLI and managing its backend matters to people who expect a package manager to control the software version. A background copy that updates separately could mean the CLI and app-server run different versions, complicating reproducibility and troubleshooting. It may also affect users who rely on a proxy or session-specific environment settings.
The reported restart behavior raises a practical concern for long-running work: an automatic backend update could interrupt an active turn, according to the linked issue cited by the reporter. A daemon that persists after its last client closes also uses background processes and storage outside the immediate CLI session. Those considerations do not establish that users will encounter every listed effect, but they explain why the reporter is asking for opt-in startup or clearer lifecycle controls.
As an affiliate, we earn on qualifying purchases.
The CLI and Managed Daemon
The report identifies the setup as npm-installed Codex CLI 0.157.0 running in WSL2. It contrasts a command-line session, which the reporter expects to use the installed executable and end when its window closes, with a shared daemon model that may suit the desktop app or Remote Control. That distinction is the user’s argument for different defaults, not a statement of OpenAI’s product rationale.
The issue links to earlier reports about daemon updates, externally managed executables, npm updates not changing the daemon version, Arch Linux package startup, and hooks receiving daemon rather than session details. It also documents the reporter’s workaround: disable daemon_auto_start, stop the daemon, manually terminate the updater if it remains, and remove the daemon package directory. This is an account of one user’s steps, not official troubleshooting guidance.
“Please make daemon_auto_start opt-in (default false) for the CLI, or at least ask once before turning it on.”
— The GitHub issue reporter
As an affiliate, we earn on qualifying purchases.
Scope and OpenAI Response
The supplied material is a single user report about version 0.157.0 on Linux under WSL2. It does not confirm whether automatic daemon startup is the default on other operating systems, for other release versions, or with installations through Homebrew or system package managers. Nor does it establish whether the described proxy and hook effects occur in all configurations.
No response from OpenAI, issue resolution, or release-note explanation is included. The report’s account of process persistence, package copying, update timing and shutdown behavior has not been independently corroborated here. It is also unclear whether the behavior is intended, a defect, or subject to configuration beyond the feature flag mentioned by the reporter.
As an affiliate, we earn on qualifying purchases.
Look for a Maintainer Update
The next concrete development would be a response or change from Codex maintainers addressing daemon_auto_start, package-manager installations and cleanup of the updater process. Readers can check the linked GitHub issue and subsequent release notes for confirmation of the default, supported controls, and any fixes to update interruptions or session-specific environment handling.
Until such information is available, the reported workaround should be treated as the reporter’s own procedure, not an official recommendation. Whether the daemon can be made to exit when its last client disconnects, and whether managed updates will remain separate from CLI package updates, remain open points in the supplied account.
As an affiliate, we earn on qualifying purchases.
Key Questions
What does the report say happens when Codex CLI starts?
The reporter says an interactive session in Codex CLI 0.157.0 starts a detached app-server daemon that continues after the CLI window closes.
Does the daemon update the CLI package itself?
According to the report, it copies the app-server package into a directory under ~/.codex and updates that daemon copy. The reporter says its version can then differ from the npm-installed CLI.
Could an update interrupt an active Codex turn?
The report links to another issue describing a 60-second drain budget before active turns may be force-stopped during an update. The supplied material does not independently verify how often this occurs.
Has OpenAI confirmed this behavior or announced a fix?
No company response or fix is included in the source material. The described behavior is attributed to a user report for version 0.157.0 on WSL2.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
