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 GitHub issue from a Codex CLI 0.157.0 user reports that opening an interactive session starts a persistent app-server daemon and updater by default. The report describes how the daemon runs from a copy in the user’s home directory and can update independently of the package-managed CLI; OpenAI has not provided a response in the supplied material.
A user of Codex CLI 0.157.0 reported that starting an interactive session automatically launches a persistent app-server daemon and a separate updater, which can keep running after the CLI window closes. The GitHub issue describes behavior on Linux under WSL2 and raises questions about background updates, package-manager versions and how the daemon handles session settings.
According to the issue, the CLI starts codex app-server –managed-daemon when an interactive session opens. The process runs without a terminal and, in the reporter’s setup, remains alive after the Codex window closes until it is stopped with a daemon command or the system reboots. The user says the daemon copies a platform package of about 374 MB into ~/.codex/packages/app-server-daemon/releases/ and runs the app-server from that location rather than directly from the npm-installed package.
The report says a detached pid-update-loop checks for updates five minutes after startup and then hourly. It can download a newer release and restart the backend, separating the backend’s version from the version installed through the user’s package manager. The reporter cites a related issue describing forced termination of active turns after a 60-second drain period during an update; that behavior is a concern raised by linked reports, not an independently verified outcome in the supplied material.
The user also says the daemon retains environment variables from the session that first started it, including an HTTPS_PROXY value set by a launch wrapper. They report that hooks in some situations may use the daemon’s working directory instead of the active session’s, and that terminal-targeting hooks may not identify the client terminal. These are reported effects and related issue references; the source does not establish how broadly they occur.
Background Updates Affect CLI Control
The reported behavior matters because it changes the relationship between a command-line tool and the software running its backend. A user who installs Codex through npm may expect the installed package to determine which executable runs and when it changes. In this report, the daemon instead runs from a separate copy and can update on its own schedule, making version management less direct.
A process that outlives its client can also retain settings from the session that launched it. If those settings include a proxy or working directory, later sessions may not behave as users expect. Separately, an update that restarts a backend could affect work in progress, although the supplied report does not confirm that a turn was interrupted in the reporter’s own case.
The issue is framed as a request to make automatic daemon startup opt-in for CLI users, while leaving it available for the desktop app or Remote Control use. That distinction reflects different expectations: a shared background service may suit persistent app features, while command-line users may prefer a process tied to the current session and the binary installed by their package manager.
As an affiliate, we earn on qualifying purchases.
How the Reported Startup Works
The source is a GitHub feature request by someone identifying their setup as Codex CLI 0.157.0, installed with npm on Linux using WSL2. It is an individual user report, not a statement from OpenAI or a published technical notice. The user asks for the daemon_auto_start feature to default to false, or for the CLI to ask before enabling it.
The report says the user disabled the feature as a workaround and then stopped the daemon. They found that daemon stop did not stop the pid-update-loop in their test; they say it was still running 70 seconds later and had to be terminated separately. They also removed the daemon’s package directory. The user reports that, with the feature disabled, a new TUI session no longer starts the daemon. These steps describe that person’s experience and should not be treated as general product guidance without confirmation.
The issue links to earlier reports about forced backend restarts during updates, support for externally managed executables, package updates not recovering a daemon version, an Arch Linux startup problem, and hooks using daemon rather than client-session details. Those references show related concerns raised by users, but the supplied material does not establish their status or whether they share one cause.
“Please make daemon_auto_start opt-in (default false) for the CLI, or at least ask once before turning it on.”
— Codex CLI user who filed GitHub issue #48195
As an affiliate, we earn on qualifying purchases.
Scope and Current Behavior Need Confirmation
The supplied source is one user’s report and does not include an OpenAI response, a maintainer explanation or confirmation that the behavior affects every installation. It also does not say whether later CLI versions changed the default, what conditions trigger the managed daemon, or whether package-manager installations are intended to use this arrangement.
The reported update timing, copied package size and retained environment reflect the filer’s setup. The material does not establish how the daemon behaves across other operating systems, installation methods or session types. Nor does it confirm that the linked hook and active-turn issues are caused by the same implementation or remain unresolved.
As an affiliate, we earn on qualifying purchases.
Maintainer Response and Version Checks
The next clear development would be a response or code change from Codex maintainers addressing the request to make daemon_auto_start opt-in or ask users before starting it. Readers should check the issue and release notes for confirmation of whether startup defaults, package-manager handling, updater shutdown or environment behavior have changed.
Until that information is available, the report supports a limited conclusion: one user running Codex CLI 0.157.0 on WSL2 observed a persistent daemon and updater start with an interactive session. Whether that behavior is intended across supported setups, and what the current default is in later versions, remains unconfirmed by the supplied source.
background update management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did the Codex CLI user report?
The user said Codex CLI 0.157.0 started a persistent app-server daemon and a separate update loop when they opened an interactive session. They reported that both could operate beyond the lifetime of the CLI window, though they say the daemon stop command did not stop the updater in their test.
Does this report confirm the behavior affects every Codex CLI installation?
No. It documents one user’s setup: an npm-installed CLI on Linux under WSL2. The supplied material does not confirm behavior across other operating systems, versions or installation methods.
Why is the daemon’s separate copy a concern?
The reporter says the daemon runs an app-server copied into the user’s Codex directory and can update independently of the npm-installed CLI. That could make the backend version and update schedule harder for a package-manager user to control; the report does not establish how broadly this affects users.
What change did the user request?
The user asked for daemon_auto_start to be opt-in by default for the CLI, or for users to be asked before it is enabled. They said automatic startup could still make sense for the desktop app, Remote Control or an explicitly started daemon.
Has OpenAI confirmed a fix or current status?
The supplied source contains no OpenAI response or fix announcement. It does not establish whether the reported behavior has changed in versions released after 0.157.0.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
