BrevFeed
Sign in
← All stories
● Covered by 1 source · 1 reportLow impact1 negative

Codex CLI version 0.157.0 installs persistent, self-updating background daemon by default

🔄 Updated 26d ago
Aggregated by BrevFeed dev · updated 26d ago
🔖 Save
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Codex CLI 0.157.0 starts a persistent background daemon by default.
  • The daemon copies its own binaries, decoupling its version from the CLI.
  • The daemon continues running after CLI sessions close.
  • Users report issues stopping all daemon-related processes.

Unexpected Daemon Behavior

The Codex CLI, starting with version 0.157.0, now automatically initiates a persistent background daemon upon opening an interactive session. This daemon, identified as `codex app-server --managed-daemon`, operates in its own session without a TTY and continues to run even after all Codex windows are closed, becoming reparented to PID 1.

Decoupled Backend and Self-Update Mechanism

The daemon copies the entire platform package, approximately 374 MB, into `~/.codex/packages/app-server-daemon/releases/<version>/`. It then runs from this copied location, effectively decoupling the backend's version from the CLI version installed via a package manager like npm. This self-updating behavior is considered unusual for a CLI tool, where the expectation is that the backend's lifecycle is tied to the CLI window and uses the installed binary.

User Concerns and Workarounds

Users have expressed concern that a persistent, self-updating background daemon should not be enabled by default without explicit user consent or a clear prompt. A workaround involves disabling `daemon_auto_start` via `codex features disable daemon_auto_start`, stopping the daemon with `codex app-server daemon stop`, and manually killing any remaining `pid-update-loop` processes, followed by removing the copied daemon files.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

Keep reading

dev New Terminal Tools Manage AI Coding Agents and Sessions 14h ago dev GitHub Copilot Enhances Efficiency with Improved Context Handling and Model Selection 1d ago dev Kubernetes Extends Reach to Desktop Infrastructure, Highlighting Database Management Challenges 1d ago releases OpenAI Releases Official Command-Line Interface (CLI) for its REST API 16d ago security Jscrambler npm Package Supply Chain Attack Deploys Infostealer 9d ago

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Primary sources

GitHub cmc_internal/api GitHub github/collect GitHub _view_fragments/issues GitHub openai/codex GitHub _private/browser GitHub get-started/accessibility

Reporting from

Hacker News Front Page — Codex CLI installs a persistent, self-updating background daemon by default 💬 Discuss on HN 26d ago →

The Codex CLI version 0.157.0 now automatically starts a persistent, self-updating background daemon, which runs independently of the CLI session and copies its own binaries. This change is unexpected for a CLI tool, as it creates a decoupled backend version and leaves background processes running even after the CLI is closed.