Codex CLI's background daemon draws fresh developer pushback
A September request to make daemon startup opt-in resurfaced in a lively October 12 discussion about update control and package-manager installs.
An old request gets a new audience
A request in OpenAI’s Codex GitHub repository to make background daemon startup optional drew a new wave of discussion on Hacker News on October 12. The issue itself was filed on September 25, so the new event is the public debate, not a newly released Codex feature. Its author says Codex CLI 0.157.0 started a persistent app-server daemon and a separate update loop after an interactive session in their Linux setup. They argue that a command-line tool should normally stop with its window and follow the version installed by the user’s package manager.
What remains in dispute
The issue author also reports a copied package, an updater that outlived a daemon-stop command, and an environment inherited from an earlier session. These are specific user reports, not findings AITrending reproduced across supported platforms. In the English Hacker News thread, some developers describe similar frustrations and share ways to disable auto-start; others argue that automatic updates have a place in rapidly changing software. The GitHub request was still open when reviewed. No cited source establishes that the reported behavior is a security breach or that OpenAI has committed to changing the default.