Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C118 Supported 2026-11-13

GitHub issue #57101 in openai/codex, opened 2026-10-26 by americanmademischief, records a report that on Windows with Codex desktop package OpenAI.Codex 26.1021.3705.0 and Computer Use plugin 26.1021.31345, a gold/yellow border remained around the display after a Codex chat had finished its native desktop capture work, with the Windows Computer Use helper still running and its Windows capture-access record still open approximately five hours after the screenshot-producing turn completed; the report asks for capture resources to be released when their owning work ends while preserving Computer Use for other chats that actually need it, and labels the lifecycle-ordering explanation a hypothesis, not a confirmed root cause.

Verbatim Excerpts from Cited Records
“A gold/yellow border remained around the user's display after a Codex chat had finished its native desktop capture work.”
— americanmademischief · openai/codex (issue 57101 opening body, What issue are you seeing section) · 2026-10-26T12:38:45Z ·GitHub Issue ↗
“Investigation found the Windows Computer Use helper still running and its Windows capture-access record still open approximately five hours after the screenshot-producing turn completed.”
— americanmademischief · openai/codex (issue 57101 opening body, What issue are you seeing section) · 2026-10-26T12:38:45Z ·GitHub Issue ↗
“The request is for capture resources to be released when their owning work ends, while preserving Computer Use for other chats that actually need it.”
— americanmademischief · openai/codex (issue 57101 opening body, What issue are you seeing section) · 2026-10-26T12:38:45Z ·GitHub Issue ↗
“The retained process was `codex-computer-use.exe`, PID 34140, directly parented by the main `ChatGPT.exe` process, PID 48532.”
— americanmademischief · openai/codex (issue 57101 opening body, Process and Windows evidence section) · 2026-10-26T12:38:45Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 22 comments were read. github-actions[bot] (2026-10-26) flagged #56941 as a potential duplicate; the opening body distinguishes it as a different primary symptom, a retained helper with system-wide UI lag rather than the lingering capture indicator and capture-access lifecycle. uzgaroth (2026-10-28), themag1n (2026-10-30, Windows 10), aidenszolosi (2026-11-06), DamianPlis (2026-11-06), praneet-bhagat (2026-11-06), lowluds (2026-11-07), js-iwashin (2026-11-10), lancanxiong-lang (2026-11-10), OverworkedStudent (2026-11-10), stefanielizeth73-art (2026-11-10), Hymenbust3r (2026-11-10), tonyloks (2026-11-11), cif0219 (2026-11-12), sappheirous (2026-11-12, with a minimal Calculator reproduction), WHREYYDS (2026-11-12), and Mailing718191 (2026-11-12) independently reproduce the persistent gold/yellow border on Windows after Computer Use turns complete, across desktop packages 26.1023 through 26.1106.6628.0. Workarounds reported: ending codex-computer-use.exe in Task Manager clears the border (aidenszolosi 2026-11-06; sappheirous and WHREYYDS 2026-11-12). HyungminYoon1 (2026-11-07) reproduced the JavaScript lifecycle omission with extracted lifecycle functions and tested a candidate patch, noting it is not a claim that a rebuilt app or the visible border has been verified. ichigoteguz (2026-11-08 and 2026-11-10) adds secondary-monitor and further recurrence reports. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #57101 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.

See also: Codex vs Cursor head-to-head comparison on 9bests