Codex CLI 默认启用持久化后台守护进程引发用户不满

OpenAI 的 Codex CLI 0.157.0 版本在默认情况下会自动启动一个持久的、自我更新的后台守护进程 1。该守护进程以独立会话无 TTY 方式运行，即使用户关闭窗口后仍会继续运行，直至手动停止或系统重启 1。用户报告此行为造成 CLI 不可用 1。

守护进程会将约 374 MB 的平台包（包含 codex、codex-code-mode-host 及捆绑的 bwrap/zsh/rg 工具）复制到本地的 ~/.codex/packages/app-server-daemon/releases/ 目录 1。启动后它会在 5 分钟内进行首次更新检查，之后每小时检查一次 1。自动更新机制可强制杀死活跃会话，且在 60 秒的 drain 预算后无法被禁用 1。此外，守护进程会继承首次启动时的环境变量设置，后续会话的相关配置被忽略 1。

用户要求将该功能改为可选配置 1。相关问题于 2026 年 9 月 25 日被报告，截至 10 月 12 日仍在活跃讨论 1。

OpenAI's Codex CLI version 0.157.0, installed via npm install -g @openai/codex, automatically launches a persistent background daemon process by default that continues running even after users close their terminal windows 1. The daemon, initiated as codex app-server --managed-daemon in a separate session without a terminal interface, remains active until manually stopped or the system is restarted 1.

The daemon copies approximately 374 MB of platform packages—including codex, codex-code-mode-host, and bundled utilities like bwrap, zsh, and rg—to the local directory ~/.codex/packages/app-server-daemon/releases/ 1. Once launched, the daemon checks for updates five minutes after startup, then continues checking hourly 1. Users reported that the auto-update mechanism can forcibly terminate active sessions with only a 60-second grace period before terminating, leaving no option to disable this behavior 1.

An additional issue arose from the daemon inheriting proxy environment variables from its initial launch session; subsequent terminal sessions' proxy settings are ignored, rendering the CLI unusable for many users 1. Users described the experience as severely problematic, with some stating they could not input anything in the CLI 1. The issue was first reported on September 25, 2026, with ongoing activity through October 12, 2026 1. Users have called for this behavior to be made optional rather than the default configuration 1.