GitHub issue #30408 in openai/codex, opened 2026-06-28 by kkkayye, records a report that the Codex app-server spawns a full set of global MCP server processes for each new thread or conversation but never kills them when threads are archived or closed, and that after 25 threads the reporter observed 133 orphaned MCP processes consuming about 9.3 GB RSS, with Codex Desktop 0.142.3 on macOS 15.x with 64 GB RAM.
Verbatim Excerpts from Cited Records
“Codex app-server spawns a full set of global MCP server processes for each new thread/conversation, but **never kills them when threads are archived or closed**. Over time, orphaned MCP processes accumulate unboundedly.”
·
openai/codex (issue 30408 opening body, Bug description section)
·
2026-06-28T03:40:13Z
·GitHub Issue ↗
“After 25 threads, observed **133 orphaned MCP processes** consuming **~9.3 GB RSS**:”
·
openai/codex (issue 30408 opening body, Actual behavior section)
·
2026-06-28T03:40:13Z
·GitHub Issue ↗
“All processes had PPID = app-server PID. The app-server holds them indefinitely.”
·
openai/codex (issue 30408 opening body, Actual behavior section)
·
2026-06-28T03:40:13Z
·GitHub Issue ↗
“The app-server does not track which MCP processes belong to which thread, and has no lifecycle management to kill MCP processes when threads end. There is also no `idle_timeout`, `reuse`, or `shared` config option for MCP servers.”
·
openai/codex (issue 30408 opening body, Root cause section)
·
2026-06-28T03:40:13Z
·GitHub Issue ↗
Counter-record: Issue remains open with 69 comments as of 2026-11-06; no maintainer resolution appears in the surveyed thread. Independent reproductions span macOS, Windows and Linux from 2026-07 through 2026-11-01, including FD exhaustion reports and Jetsam-level memory pressure, with the latest surveyed reproductions by tahuy on 2026-10-30 and eduarbo on 2026-11-01. Community members proposed patches (goodyang227 on 2026-08-24, luochen211 on 2026-09-01) and cleanup tools, with no maintainer merge or fix verdict in the surveyed thread. Surveyed thread contains no maintainer fix or closure. The claim documents only the original report, not a verified current state.
Falsification probe: If issue 30408 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.