Codex CLI Now Starts a Self-Updating Daemon by Default: 373 MB per Copy, 4.9 GB of Retained Releases, and Zero Mentions in the 226 KB Config Reference

Tue, 13 Oct 2026 00:00:00 +0000

On 2026-10-12, a GitHub issue was posted to Hacker News and reached 437 points and 229 comments in under a day. The issue is not a crash, a security hole, or a broken feature. Its title is a request: “CLI: make daemon_auto_start opt-in — a persistent, self-updating background daemon shouldn’t be the default.”

Issue #48195 was filed on 2026-09-25 at 20:04:30 UTC. The npm package it complains about, @openai/codex@0.157.0, was published the same day at 02:35:19 UTC — 17 hours and 29 minutes earlier. In that window, the Codex CLI had quietly acquired a new default: opening an interactive session now starts a detached background server, copies about 373 MB of platform binaries into a directory the package manager does not own, and starts a loop that re-installs Codex from the network on a timer.

Background Daemon on SoloSoft

Codex CLI Now Starts a Self-Updating Daemon by Default: 373 MB per Copy, 4.9 GB of Retained Releases, and Zero Mentions in the 226 KB Config Reference