跳到主要內容

Codex CLI背景Daemon評測:預設常駐,無提示安裝 | Codex CLI Daemon Review: Silent Install, No Opt-Out

By Kit 小克 | AI Tool Observer | 2026-10-18

🇹🇼 Codex CLI背景Daemon評測:預設常駐,無提示安裝

最近開發者社群最熱的話題不是新模型,而是 Codex CLI 背景Daemon 爭議:OpenAI 從 Codex CLI 0.157.0 版開始,預設把一個會自動更新的背景常駐程式(daemon)裝進使用者電腦,完全沒有跳出任何提示或選擇退出的畫面。這篇文章整理這個 Codex CLI 背景Daemon 到底做了什麼、為什麼開發者生氣,以及怎麼手動關掉它。

Codex CLI 背景Daemon 做了什麼事

根據多篇技術部落格的拆解,Codex CLI 從 0.157.0(2026 年 9 月 25 日發布)開始,只要你互動式啟動一次 codex,背後就會悄悄啟動一個常駐服務,就算你關掉終端機視窗,這個 daemon 依然在背景運行。更麻煩的是:

  • 它會把大約 374MB 的二進位檔複製到你的家目錄
  • 每小時自動檢查並更新自己
  • 啟動 daemon 的那個 session 的環境變數會被「鎖住」,之後新的 session 會沿用舊的環境變數——例如某個 session 設的 proxy,會悄悄滲透到下一個不相關的 session

而且官方的 Codex config 文件完全沒提到這個 daemon 或關閉開關,沒有任何 changelog 寫明「我們要在你的機器裝一個常駐程式」。

開發者為什麼炸鍋

這件事在 Hacker News 上討論度很高,一則要求 OpenAI 把它改成「選擇加入(opt-in)」的 GitHub issue 在 10 月 12 日衝上 602 點、292 則留言。開發者的不滿點很單純:靜默安裝常駐程式、沒有提示、沒有文件,是對使用者信任的背叛。截至 10 月 14 日,OpenAI 官方還沒有正式回應這個 issue。

如何手動關閉 Codex CLI 背景Daemon

如果你不想讓 Codex CLI 背景Daemon 一直吃你電腦資源,社群目前整理出幾種做法:

  • 執行 codex features disable daemon_auto_start 阻止新 session 啟動它
  • 執行 codex app-server daemon stop 停掉已經在跑的 daemon
  • 在 ~/.codex/config.toml 的 [features] 區塊設定 daemon_auto_start = false
  • 徹底移除:rm -rf ~/.codex/packages/app-server-daemon

小克的建議:如果你把 Codex CLI 用在公司或客戶的機器上,先檢查一下背景有沒有這個常駐程式,尤其是環境變數外洩這點,對共用機器或 CI 環境是真實風險,不是危言聳聽。

好不好用,試了才知道。


🇺🇸 Codex CLI Daemon Review: Silent Install, No Opt-Out

The hottest developer story this week is not a new model release, it is the Codex CLI background daemon controversy. Starting with Codex CLI 0.157.0, OpenAI quietly made its coding CLI install a persistent, self-updating background daemon by default, with zero prompt and no opt-out screen. Here is what the Codex CLI background daemon actually does, why developers are furious, and how to turn it off.

What the Codex CLI Background Daemon Does

According to multiple technical writeups, since version 0.157.0 (released September 25, 2026), simply starting codex interactively once spins up a backend server that keeps running even after you close every terminal window. On top of that:

  • It copies roughly 374MB of binaries into your home directory
  • It checks for and installs updates on its own, every hour
  • It locks in the environment variables of whatever session first started it, so a proxy setting from one session can silently leak into a completely unrelated later session

OpenAI's own Codex config reference does not mention the daemon or any switch for it, and there was no changelog entry announcing a persistent background process being installed on your machine.

Why Developers Are Furious

The story blew up on Hacker News: a GitHub issue asking OpenAI to make the daemon opt-in hit 602 points and 292 comments after being posted on October 12. The complaint is simple: silently installing a persistent process with no prompt and no documentation is a trust violation, not a feature. As of October 14, OpenAI had not responded to the issue.

How to Disable the Codex CLI Background Daemon

If you do not want the Codex CLI background daemon quietly eating resources on your machine, the community has worked out a few fixes:

  • Run codex features disable daemon_auto_start to stop new sessions from spawning it
  • Run codex app-server daemon stop to kill a daemon that is already running
  • Set daemon_auto_start = false under [features] in ~/.codex/config.toml
  • Fully remove it with rm -rf ~/.codex/packages/app-server-daemon

My take: if you run Codex CLI on a shared machine, a client box, or a CI runner, check for this daemon now. The environment-variable leak in particular is a real risk on shared infrastructure, not just a privacy nitpick.

You won't know until you try it.

Sources / 資料來源

延伸閱讀 / Related Articles


AI 工具觀察站 — 每日精選 AI Agent 與工具趨勢
AI Tool Observer — Daily curated AI Agent & tool trends

留言

這個網誌中的熱門文章

Google Ironwood TPU v7 推理專用晶片解析:效能追平 NVIDIA、成本低 44%,AI 晶片戰爭正式開打 | Google Ironwood TPU v7 Explained: Matching NVIDIA Performance at 44% Lower Cost — The AI Chip War Heats Up

Claude Code 實測:AI 幫你寫程式到底行不行? | Claude Code Review: Can AI Really Code for You?

Cursor vs GitHub Copilot vs Claude Code:AI 程式助手大比拼 | AI Coding Assistants Compared: Cursor vs GitHub Copilot vs Claude Code