Windows Codex app leaves backend helper processes running when closed via window X
Resolved 💬 3 comments Opened Apr 13, 2026 by argifford Closed Apr 13, 2026
What version of the Codex App are you using (From “About Codex” dialog)?
Codex app for Windows 26.409.20454
What subscription do you have?
Enterprise
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Closing the Codex app using the titlebar X does not fully shut down backend helper processes. Using File -> Exit shuts down cleanly.
What steps can reproduce the bug?
- Open the Codex app on Windows.
- Wait for startup to finish with MCP tools enabled.
- Close the app with the window X.
- Inspect running processes in Task Manager or PowerShell.
What is the expected behavior?
All Codex-related processes exit.
Actual:
Backend/helper processes remain running after the window closes, including:
- codex.exe (app-server)
- uvx.exe
- node.exe
Additional information
Notes:
- On this machine, File -> Exit is clean.
- The issue appears specific to the window-close path.
- The remaining helper processes appear to be MCP-related children.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗