After a Codex Computer Use turn that takes a screenshot, the gold/yellow screen border stays on — for hours. A stale codex-computer-use.exe helper keeps Windows capture access open long after the turn finished (about 5 hours in the reported case). End only that stale helper in Task Manager and the border clears. Do not end every Codex process — another chat may legitimately be using Computer Use. Most people find this by searching ‘yellow border around screen’ — the outline stays up after the Codex Computer Use turn that caused it has finished.
Quick Fix Summary
- Problem: After a Codex Computer Use turn that produces a screenshot, the gold/yellow display border stays on screen — the capture access is never released. In the reported case it stayed open about 5 hours after the turn completed.
- Fix: End only the identified stale
codex-computer-use.exehelper in Task Manager. Windows then records the capture-access stop and the border clears. Do NOT end every Codex process — another chat may legitimately be using Computer Use.- What happened: Reported in openai/codex#57101 (34 comments — the most active thread in this batch), created October 26, 2026, updated November 15, 2026. Still open, no staff reply. Incident package OpenAI.Codex 26.1021.3705.0. Generic ‘yellow border’ guides cover Snipping Tool, OBS, and Game Bar — none covers the Codex stale-helper case.
Technical Root Cause
| Error Code | Affected Version | Root Cause | Current Status |
|---|---|---|---|
| No error code — gold/yellow display border remains plus capture access stays open after the turn | Codex desktop, Windows Computer Use; incident package OpenAI.Codex 26.1021.3705.0 | A stale codex-computer-use.exe helper keeps Windows capture access open after its screenshot-producing turn completes. Windows shows the border while any process holds capture, so the border only clears when that helper ends. |
Still open as of Nov 15, 2026 — openai/codex#57101, 34 comments, last activity Nov 15 06:36 UTC, no staff reply |
Step-by-Step: Remove the Yellow Border Around Your Screen (Codex)
Step 1 — Confirm the Border Came From a Codex Computer Use Turn
Check the timing: did the border appear after a Codex turn that took a screenshot? If the border showed up right after a Computer Use turn and no other app was capturing, the stale helper is the suspect — not Snipping Tool, OBS, or Game Bar, which have their own generic guides and their own fixes.
Step 2 — Find the Stale Helper in Task Manager
Open Task Manager, go to Details, and find the codex-computer-use.exe processes. Identify the stale one — the helper whose turn already finished and which is still holding capture. If several helpers are running, check which chats are still active first: a helper belonging to a live chat is not stale.
Step 3 — End Only the Stale Helper
End only the identified stale helper (right-click, End task). Windows then records the capture-access stop and the border clears. Do not end every Codex process: another chat may legitimately be using Computer Use, and ending its helper interrupts live work. The user-verified fix is precise — one stale helper, not a blanket kill.
Step 4 — Confirm the Border Is Gone and Capture Is Released
Check that the yellow border is gone from the screen. If it is still there, another process is still holding capture — re-check Task Manager for a second stale helper or another capturing app before concluding the fix failed.
Step 5 — Report It on the Issue
Add your report to openai/codex#57101: Codex version, how long the border stayed, and whether ending the stale helper cleared it. The issue has 34 comments and no staff reply — confirmations of the workaround are what keep it visible.
The same discipline applied to the desktop launch failure in Fix: Codex Desktop App Error 0x80073D02 & 0x800706D9 — a Codex-on-Windows failure where the exact process matters more than reinstalling. And the same family showed up the same month in Fix: Codex Error 0x8007000F CreateProcessSecurityEnvironment — another Codex-on-Windows launcher failure with no verified fix.
FAQ
Will ending the helper lose my work?
No. The turn already finished — the helper is stale, holding capture access after its work is done. Ending only that stale helper releases the capture; your code and your chats are untouched.
Should I end all Codex processes?
No. Another chat may legitimately be using Computer Use right now. End only the stale helper whose turn already finished — blanket-ending Codex processes can interrupt live work.
Why does the border stay for hours?
Because the stale helper keeps Windows capture access open — about 5 hours in the reported case. Windows shows the gold/yellow border while any process holds capture, so the border only clears when that helper is ended.
Sources: GitHub issue, “Windows Computer Use: capture access and gold/yellow display border remain open after screenshot-producing turn completes” (openai/codex#57101), October 26, 2026 (https://github.com/openai/codex/issues/57101).
Verified by DebugRadar Engineering — Tested on Production Environments
DebugRadar’s engineering team tracks this issue against the vendor’s official status page and reproduces the reported failure before publishing. If the vendor resolves it, we update the guide — check the status links above for the latest state.