SignalTech/AI
Codex CLI installs a persistent, self-updating background daemon by default
Codex CLI's default persistent self-updating daemon raises security and system control concerns.
Context
What happened: A GitHub issue asks OpenAI to make the Codex CLI daemon_auto_start opt-in. Since version 0.157.0, opening an interactive session starts a persistent background daemon that keeps running after all Codex windows close.
Key numbers: Version 0.157.0, installed via npm install -g @openai/codex on
Why it matters: The reporter says the backend version becomes decoupled from the installed CLI and can self-update, so the process serving a later turn may not be the artifact the user installed. A commenter says such processes should not appear on small version bumps without notice.
What changed
A GitHub issue asks OpenAI to make the Codex CLI daemon_auto_start opt-in. Since version 0.157.0, opening an interactive session starts a persistent background daemon that keeps running after all Codex windows close.
Why it matters
The reporter says the backend version becomes decoupled from the installed CLI and can self-update, so the process serving a later turn may not be the artifact the user installed. A commenter says such processes should not appear on small version bumps without notice.