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 about Codex CLI 0.157.0 says opening an interactive session starts a persistent app-server daemon and an updater that checks for releases hourly. The report describes effects on version control, session environment and hooks, but these details come from one GitHub issue; the source material does not establish how broadly users are affected or whether OpenAI has responded.
A user of Codex CLI 0.157.0 says that opening an interactive session starts a persistent app-server daemon and a separate updater without asking first. The report matters to CLI users because the background process can outlive the terminal session, use the environment of the session that launched it and update its backend independently of the installed CLI; the available source is a single GitHub issue, not an OpenAI statement.
The issue describes a CLI installed globally with npm on Linux under WSL2. According to its author, starting an interactive session launches codex app-server --managed-daemon in a detached session with no terminal. It remains running after Codex windows close, until stopped with the daemon command or the machine reboots. The report says the process copies a platform package of about 374 MB into the user’s ~/.codex directory and runs the app-server from that copy.
The author also says a detached pid-update-loop checks for updates five minutes after startup and then hourly, downloading releases and restarting the backend. The issue points to a related report saying an update can force-stop active turns after a 60-second drain period. The author says the daemon retains environment variables from the session that started it, including its HTTPS proxy setting, and reports that hooks in remote mode may receive the daemon’s working directory instead of the active session’s. These are user-reported behaviors; the supplied material does not independently verify them.
The issue requests that automatic startup be opt-in or prompt users before enabling it. As a workaround, its author says disabling the daemon_auto_start feature prevents a new TUI session from spawning the daemon. They also report that codex app-server daemon stop stopped the app-server but left the updater process running, which they terminated separately.
Control Over CLI Processes and Updates
If the behavior described is representative, it changes how users may expect a command-line tool to run: closing a session does not necessarily end its backend, and the daemon may run a version that no longer matches the package-manager-installed CLI. That can complicate version management and troubleshooting, especially for people who rely on npm or a Linux package manager to control software updates.
The reported environment and hook effects also have practical consequences. A shared process carrying one session’s proxy settings or working directory could behave differently from a later session. The issue therefore raises questions about process lifetime, update control and session isolation. The source does not show how often these effects occur or whether they affect users beyond the reporter.
As an affiliate, we earn on qualifying purchases.
The issue distinguishes between CLI use and other Codex use cases. Its author says a shared daemon could make sense for Remote Control or the desktop app, or when a user explicitly starts or bootstraps it. For ordinary CLI sessions, the author prefers a backend that follows the terminal session, uses the installed executable and does not update in the background.
The report links to related GitHub issues concerning forced termination of active turns during updates, externally managed app-server executables, recovery after npm updates, Arch Linux startup problems and hooks receiving unexpected session or terminal details. Those links indicate that users have raised adjacent concerns, but the provided material does not establish that all share the same cause or that each remains unresolved.
“Please make daemon_auto_start opt-in (default false) for the CLI, or at least ask once before turning it on.”
— The GitHub issue author
As an affiliate, we earn on qualifying purchases.
Scope and Fix Status Remain Unknown
The supplied source is one user’s report for version 0.157.0 on Linux under WSL2. It does not include an OpenAI response, a confirmed explanation of the intended behavior, or evidence about the number of affected users and platforms. It also does not establish whether the linked issues describe the same underlying defect.
It remains unclear whether the default is a deliberate product change, whether package-manager installations are meant to use the copied daemon release, and whether the updater process is expected to stop with the daemon. The issue’s filing date and present resolution status are not included in the provided material.
As an affiliate, we earn on qualifying purchases.
Watch for Maintainer Response
The next concrete development would be a maintainer response or change to the issue, such as clarifying the intended CLI behavior, documenting how to disable automatic startup or changing the default. Users evaluating the report can check the linked issue and related reports for updates, while treating the described effects as reported behavior until they are independently confirmed.
The source material gives no announced fix, release date or commitment. Whether the daemon’s lifetime, update policy and cleanup behavior will change remains open.
As an affiliate, we earn on qualifying purchases.
Key Questions
What does the report say Codex CLI starts?
It says an interactive session starts a persistent app-server daemon and a detached updater that checks for releases after five minutes and then hourly.
Which version and setup does the issue describe?
The author identifies Codex CLI 0.157.0, installed globally through npm, running on Linux under WSL2.
Does the source confirm that all Codex CLI users are affected?
No. It is a single-user report and does not establish the behavior’s prevalence across users, operating systems or installation methods.
What workaround does the author report?
The author says disabling daemon_auto_start prevented a new TUI session from spawning the daemon. They also report that stopping the daemon left the updater running, which they terminated separately.
Has a fix been announced?
No fix or release commitment appears in the supplied material. The issue’s current status and any maintainer response are not provided.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
