- Since 0.157.0, opening an interactive session in the terminal starts a background program (daemon), according to the issue author. It keeps running after the window closes until the daemon stop command or a reboot.
- According to the author, the daemon copies the entire installed npm package (about 374MB) under ~/.codex/packages and runs from that copy. A separate updater fetches new releases every hour starting 5 minutes later and restarts the backend. The author writes that a restart may interrupt work in progress.
- The daemon keeps the proxy environment variables from the first session it started. Reports say that later proxy changes in other sessions are not applied. The author thinks this has the same cause as related issues.
- The author's temporary workaround is to turn off the daemon_auto_start feature, run daemon stop, and stop the updater process separately. The issue links to a commit that disables the default (title: codex: disable daemon auto-start by default), but the source alone does not show whether it was merged or released.
What bothers me more than the daemon staying alive after the window is closed is that the auto-updater can cut off work that is in progress. If you switch proxies from session to session, the environment from the first session sticking around would also be a real headache. This report comes from a Linux (WSL2) environment, so I'm curious whether anyone has checked on another setup whether the updater stays running after daemon stop.