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 about Codex CLI 0.157.0 reports that opening an interactive session starts a persistent background app-server daemon and updater. The report describes copied binaries, inherited environment settings and possible disruption from updates, but these details come from one user’s account; the issue does not include an OpenAI response.
A Codex CLI user has asked OpenAI to make the app-server daemon opt-in after reporting that version 0.157.0 starts a persistent background service when an interactive session opens. The report matters to CLI users because it says the service can continue after the window closes, update separately from the installed CLI, and retain environment settings from the session that launched it.
The report, filed as GitHub issue #48195, identifies the setup as Codex CLI 0.157.0 installed with npm on Linux under WSL2. The user says opening an interactive session starts codex app-server --managed-daemon. According to the report, it runs without a terminal and remains after the Codex window closes until stopped with a daemon command or the system reboots.
The user says Codex copies a roughly 374 MB platform package into ~/.codex/packages/app-server-daemon/releases/<version>/ and launches the service from that copy. The report also describes a detached updater that checks for updates five minutes after startup and then hourly. The author says this can leave the daemon’s version independent of the npm-installed CLI and that an update restart may interrupt active turns.
The issue raises operational concerns beyond background activity. The user says the daemon inherits environment variables from whichever session starts it, including a per-invocation HTTPS proxy, and reports hook behavior involving the daemon’s working directory and terminal identity. They also say stopping the daemon did not stop its separate updater process. These are the reporter’s observations; the issue text provided does not establish how broadly they apply across installations or configurations.
Background Updates and CLI Control
If the reported behavior is reproducible, it changes what users may expect when they launch a command-line tool: the backend can outlast the session and operate on its own update schedule. Users and administrators who manage software through npm or another package manager may want the running backend to follow that managed installation rather than a separate copy that updates independently.
The reported environment inheritance could also matter in setups that rely on session-specific proxy settings or hooks. A daemon started under one configuration may serve later sessions, according to the report. The issue does not quantify how many users are affected, nor does it establish that every listed hook or update concern occurs in typical use. It does, however, identify concrete questions about process lifetime, version control and session isolation for CLI users.
Linux WSL2 background process manager
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
The issue distinguishes the command-line interface from use cases such as Remote Control or the desktop app. The reporter says a persistent shared daemon may make sense in those settings, while arguing that CLI users should be able to keep the backend tied to the window and the binary installed by their package manager. The requested change is to make daemon_auto_start default to false or ask users before enabling it.
The author cites related GitHub issues concerning forced termination of active turns during daemon updates, externally managed daemon executables, version mismatches after npm updates, Arch Linux startup problems, and hooks receiving daemon rather than session details. Those references show that the report connects its request to other tracked concerns; they do not, by themselves, confirm that each issue shares one cause or has the same status.
“Please make daemon_auto_start opt-in (default false) for the CLI, or at least ask once before turning it on.”
— The issue author
As an affiliate, we earn on qualifying purchases.
Scope and OpenAI Response
The source material contains a user’s issue report, not an OpenAI confirmation or a documented product-wide explanation. It does not show whether the behavior is intentional, whether it affects CLI versions or operating systems beyond the reported setup, or whether a configuration change is planned. The precise scope of the reported updater, proxy inheritance and hook behavior also remains unclear from the supplied material.
The report gives a workaround involving disabling daemon_auto_start and stopping the daemon, but says the updater process remained alive and required separate termination. That account has not been independently verified here. The supplied issue text also does not state whether the report has since been acknowledged, resolved or superseded.
As an affiliate, we earn on qualifying purchases.
Maintainer Response and Fixes
The next clear development would be a response or code change from the Codex maintainers addressing whether automatic daemon startup should remain the CLI default. Users tracking the issue can look for clarification on opt-in behavior, package-manager-managed executables, updater shutdown and whether active sessions can be interrupted during updates.
Until maintainers clarify the behavior, the report advises readers only indirectly: it records one user’s workaround and configuration, rather than documenting an official recommendation. Any wider conclusions depend on further reports, reproducible testing across supported installation methods, or a maintainer explanation.
session environment variable 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 author of GitHub issue #48195 says Codex CLI 0.157.0 starts a persistent app-server daemon when an interactive session opens, and also starts a separate updater.
Does the report show that every Codex CLI installation behaves this way?
No. The report names one setup: npm-installed Codex CLI 0.157.0 on Linux under WSL2. The supplied material does not establish behavior across other versions, operating systems or installation methods.
What changes is the reporter asking for?
The user asks for automatic daemon startup to be off by default in the CLI, or for Codex to ask before enabling it. The report also proposes changes to daemon shutdown and package-manager handling.
Has OpenAI said whether it will change the default?
No response or commitment from OpenAI appears in the supplied issue material. Whether the request will lead to a change remains unknown.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
