Day 7 receipt
Codex CLI 0.157.0
The release that turned on an automatic background server for interactive Codex CLI sessions and added GPT-6 Sol and Luna.
Launch dayWhat they claimed, quoted word for word · 4
“Enabled automatic background-server startup for eligible interactive sessions, with recovery choices when server settings are incompatible.”
It started automatically, but on some Windows and Arch setups the 'recovery choice' was a hard error telling users to rerun with --no-daemon. Users also found the server outlives every window and updates itself hourly.
“Added GPT-6 Sol and Luna, including Amazon Bedrock support and migration prompts for older models.”
No solid user reports either way in this scan.
“Fixed configured proxy routing for realtime connections and standalone web search, including search redirects.”
Not contradicted directly. One report says the new daemon keeps the proxy settings of whichever session started it, which is a separate problem.
“Added retries for transient file-upload failures and increased the upload timeout to five minutes.”
No solid user reports either way in this scan.
Day 7What real users report · 6
A CLI user documents that opening a session now starts a persistent background daemon that keeps running after every window closes, copies a ~374 MB package into the Codex folder and runs an hourly self-updater. They ask for it to be opt-in and share the steps they used to switch it off.
Open as of 16 Oct; many +1 comments · Open the source
0.157.0 refuses to start on Windows with a daemon privilege error that says to use a non-elevated terminal or --no-daemon; the reporter says 0.156.1 works.
Open as of 16 Oct · 63 comments · 50 reactions · Open the source
0.157.0 would not start on some Windows machines. Maintainers reproduced it and published 0.157.1 as a hotfix.
Closed as completed · 34 comments · Open the source
After the daemon was installed, several terminal windows flashed open and shut on every request on Windows. Fixes landed in later releases, and some users also had to update the daemon itself.
Closed as completed · 153 comments · 164 reactions · Open the source
After upgrading the Arch Linux package to 0.157.0, plain `codex` no longer opened a usable session unless run with --no-daemon; the reporter reproduced it with a clean config folder.
Open as of 16 Oct · Open the source
The opt-in request reached the Hacker News front page, where the default-on, self-updating daemon was the main complaint.
607 points · 292 comments · Open the source
Verified fixes (from Unstuck)3
stop Codex CLI from running a persistent self-updating background daemon
The daemon is controlled by the daemon_auto_start feature flag. The issue reporter's working opt-out: turn the flag off, stop the daemon, kill the leftover updater loop and remove the copied package.
Codex CLI 0.157.0 won't start on Windows ('host Job Object prevents ...')
Codex maintainers reproduced the failure inside nested Windows Job Objects and published 0.157.1 as a hotfix. Update the CLI.
terminal windows keep flashing on Windows while Codex works
OpenAI published fixes (0.159.2, then more in 0.161.x); the daemon must be updated too. Several users only got rid of the windows after re-pinning the daemon to the current CLI with codex app-server daemon update --from-cli.