← Tuesday, October 13, 2026AgentsNews

Codex CLI starts a persistent, self-updating daemon by default

github.com 8 min read Editor score 7/10

A Codex CLI issue reports that opening an interactive session launches a managed daemon that persists after the window closes and copies a platform package of about 374 MB. Agent developers should check background-process behavior, update paths and resource use in their own tools.

What
A Codex CLI 0.157.0 issue report says opening an interactive session starts a persistent app-server daemon by default.
How
The reported daemon copies the platform package and launches an updater that checks after five minutes, then hourly, and restarts the backend.
Why it matters
Daemon persistence can decouple backend versions from package-managed CLI versions and retain a session's proxy environment.
starts starts restarts CLI app-server--managed-daemon pid-update-loop backend
The CLI starts a managed daemon, whose updater can restart the backend. Sketched from the article's own text.

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.

Your note

Private to you. Stored in this browser, and synced to your account when you are signed in.