Codex CLI update installs persistent self-updating background daemon

A recent update to Codex CLI introduces a self-updating background daemon that persists after the user exits the harness. The daemon initially checks for updates every five minutes, then switches to hourly checks, and restarts itself upon detecting a new version. This restart process interrupts any currently in-process turns. The daemon does not terminate when the user quits the CLI; it only stops if the user runs a specific Codex command to stop the server or reboots the machine. A bug was identified where the daemon did not fully quit, indicating sloppy coding in the production release.

This behavior contrasts with standard terminal command expectations where processes end upon completion, raising concerns about background hygiene and potential similarities to rootkit behavior, though implemented by developers to keep users on the latest version. The discussion criticizes the feature as poor hygiene that disrupts active sessions and violates user expectations for command-line tools, noting that the rapid release pace of agentic harnesses is prioritizing mindshare over operational stability. The implementation has drawn scrutiny for its impact on user control and system stability.