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 user says version 0.157.0 starts a persistent background app-server daemon when an interactive session opens. The reporter says it copies a roughly 374 MB platform package, retains the launching session’s environment and checks for updates hourly; these are user-reported observations, not a confirmed OpenAI response. The issue asks OpenAI to make auto-start opt-in and reports that stopping the daemon may leave its updater running.
A Codex CLI user has reported that version 0.157.0 starts a persistent app-server daemon when an interactive session opens, with the daemon able to update itself after the CLI window closes. The GitHub issue asks OpenAI to make this behavior opt-in, citing concerns about background processes, package-manager updates and session-specific settings.
The reporter says the behavior occurred on Linux under WSL2 after installing Codex CLI through npm. According to the issue, starting an interactive session launches codex app-server --managed-daemon in a detached process that continues after the client closes. The user says it remains active until stopped with a daemon command or until reboot.
The issue describes the daemon copying a platform package of about 374 MB into ~/.codex/packages/app-server-daemon/releases/ and running from that copy. The reporter says a separate updater process checks for updates five minutes after startup and then hourly, downloading releases and restarting the backend. The size, timing and behavior are the reporter’s account; the issue material does not include an OpenAI response confirming them.
The user also reports that the daemon keeps environment variables from the session that launched it. In their example, a proxy set for one invocation continued to affect the daemon’s outbound connections when later sessions were started. The issue links to other reports about active turns being interrupted during updates, externally managed executables, npm updates leaving the daemon on an older version, package compatibility and hooks receiving the daemon’s working directory or terminal context.
Control Over CLI Background Processes
The report raises a practical distinction between a command-line tool that runs only while a user’s session is open and one that leaves a persistent background service. Users may reasonably expect a CLI installed through a package manager to use the installed executable and follow that manager’s update process; the reported daemon instead maintains a separate copy and update path.
That separation could affect how users manage versions, diagnose behavior and apply network settings. The reporter also points to a linked issue describing updates that can force-restart the backend after a 60-second drain period, potentially ending active turns. These are concerns documented in related issue reports, not independently established outcomes for every user or installation.
The design may serve other Codex modes differently. The reporter says a shared, self-updating backend could make sense for Remote Control or the desktop app, while arguing that CLI users should be asked before it is enabled. The core product question is whether the same default should apply across those use cases.
As an affiliate, we earn on qualifying purchases.
How the Daemon Is Reported to Work
The issue identifies the installation as Codex CLI 0.157.0, installed with npm install -g @openai/codex on Linux in WSL2. The reported trigger is opening an interactive session, rather than explicitly running a daemon-start command. The daemon is described as detached from the client terminal and reparented to the system’s init process after the original session ends.
The reporter says users can disable automatic startup with codex features disable daemon_auto_start, then stop the app-server daemon. However, their report says codex app-server daemon stop did not stop the separate pid-update-loop process in their test. They describe manually terminating that updater and removing the daemon’s package directory as part of their workaround. This is a single user’s account; the source does not establish how commonly the issue occurs or whether the workaround is appropriate for other setups.
The report references related GitHub issues, including one about auto-updates interrupting active turns and others concerning externally managed executables, package updates and hook behavior. Those links provide context for the user’s concerns but do not, by themselves, establish that all issues 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.
Open Questions About Scope and Shutdown
The source material does not include an OpenAI response, a status update or confirmation that the behavior is intended across all CLI installations. It also does not establish whether the issue has been reproduced on operating systems or installation methods beyond the reporter’s npm-on-WSL2 setup, or whether later CLI versions behave the same way.
It remains unclear whether the daemon’s copied executable and updater are expected for every CLI user, whether package-manager installations are meant to be treated differently, and whether the reported updater process remaining after a stop command is a known bug. The related reports raise compatibility and interruption concerns, but the provided material does not show their resolution or prove a shared cause.
As an affiliate, we earn on qualifying purchases.
Maintainer Response and Default Behavior
The next concrete development would be a response or resolution on GitHub issue #48195 addressing whether daemon_auto_start should be opt-in, prompt users, or remain enabled for CLI sessions. A response could also clarify whether package-manager installations should run their managed binary and how the daemon and updater are meant to stop.
Until maintainers clarify the behavior, the report describes a user-side way to disable auto-start, but readers should treat it as the reporter’s workaround rather than official guidance. The issue material gives no announced fix, release date or confirmed change to the default.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did the Codex CLI user report?
The user says Codex CLI 0.157.0 launches a persistent app-server daemon when an interactive session opens, and that a separate process updates it after the session closes.
Does the report confirm that every Codex CLI installation behaves this way?
No. The report describes one setup: npm-installed CLI on Linux under WSL2. The supplied material does not confirm the behavior across other platforms, installation methods or versions.
What does the reporter say the daemon does?
According to the issue, it runs after the CLI window closes, uses a copied platform package of about 374 MB, retains the launching session’s environment and checks for updates five minutes after startup and then hourly.
Has OpenAI said it will change the default?
The source material includes a feature request but no maintainer response or announced change. Whether automatic startup will become opt-in remains unconfirmed.
What shutdown issue does the reporter describe?
The user says the daemon stop command ended the app-server but left the pid-update-loop updater running in their test. The issue material does not establish how often this happens or whether it has been fixed.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
