Urgent.News

What's breaking now, across thousands of outlets.

Tech

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

The Codex CLI version 0.157.0, installed via the `npm install -g @openai/codex` command on Linux using WSL2, now installs a persistent, self-updating background daemon by default. This daemon starts automatically when users open an interactive Codex session, running in its own session with no TTY and keeping running after every Codex window is closed.

The entire 374 MB platform package, consisting of the `codex`, `codex-code-mode-host`, and bundled `bwrap`, `zsh`, and `rg`, is copied into `~/.codex/packages/app-server-daemon/releases/` and managed by the daemon. Additionally, a detached updater checks for updates every 5 minutes and hourly, downloading new releases and restarting the backend, which can potentially disrupt active sessions.

This self-updating daemon is coupled to the CLI version, making it decoupled from the package manager installation. The report suggests that making the daemon **opt-in (default `false`)** would be more intuitive for the CLI, as it would align the backend's lifecycle with the window, run the installed binary, and avoid background updates.

The current setup, however, automatically starts, starts updating the backend, and pins the environment of the session that launched it.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at github.com →

More in Tech

Schema Markup: How to Audit It Before Google Ignores It

I work at SEOSage, which builds desktop SEO audit software. The steps below work with any crawler. Schema does not buy you rankings. It buys you eligibility. Structured data is not a ranking factor.

  • Schema markup improves rich results visibility.
  • Common schema issues: missing, broken, or irrelevant markup.
  • Validate with Google's Rich Results Test before updates.

More from Monday 12 October →