Codex CLI installs a persistent, self-updating background daemon by default
A developer has raised an issue regarding the Codex CLI, requesting that its persistent background daemon be made an opt-in feature rather than a default. The user highlights technical frustrations with the daemon's behavior, including forced updates and session interference.
Why it matters
It reflects common developer friction points regarding intrusive software behavior and the balance between convenience and user control in CLI tools.
Code Issues 5k+ ( 5k+ ) Pull requests 165 ( 165 ) Only collaborators can create PRs Discussions Actions Security and quality 1 ( 1 ) Insights More items CLI: make daemon_auto_start opt-in — a persistent, self-updating background daemon shouldn't be the default #48195 New issue Copy link New issue Copy link Open Open CLI: make daemon_auto_start opt-in — a persistent, self-updating background daemon shouldn't be the default #48195 Copy link Labels CLI Issues related to the Codex CLI Issues related to the Codex CLI app-server Issues involving app server protocol or interfaces Issues involving app server protocol or interfaces enhancement New feature or request New feature or request Description Yihua-Liu-1997 opened on Sep 25, 2026 Issue body actions What variant of Codex are you using? CLI — 0.157.0, installed via npm install -g @openai/codex , Linux (WSL2)
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in