🛠️Codex Daemon Now Opt-In, Major Changes to Backend Persistence
Codex daemon now runs in the background, persistently
TL;DR
Codex daemon is now opt-in, running in the background independently of Codex windows. This change affects how the backend is updated and maintained, with implications for session management and proxy variables.
Codex has made the daemon opt-in, meaning it no longer runs automatically with every Codex window. The daemon now runs in its own session, persists after window closure, and updates itself hourly. This impacts session management, proxy variables, and how updates are handled. The daemon's version is decoupled from the CLI version, and it starts a detached updater that checks for updates every 5 minutes and then hourly. Codex users need to manage the daemon manually now, with implications for session persistence and environment stability.
Key Points
Daemon runs in its own session, persists after window closure, starts updater 5 minutes after start.
Updater checks for updates hourly, downloads new releases, restarts backend automatically.
Daemon version decoupled from CLI version, updates independently of package manager updates.
Daemon copies platform package into ~/.codex/packages/app-server-daemon/releases/<version>/.
Daemon starts with first session's proxy variables, maintains these variables across updates.
Why It Matters
If you're managing Codex sessions in a production environment, this change impacts session persistence and backend stability. The daemon's decoupling from the CLI version means updates are handled independently, requiring careful management. Smaller teams might prefer the simplicity of the old behavior, while larger teams may benefit from the flexibility of the new system.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,569 builders reading daily.