Windows App: stale processes
Resolved 💬 4 comments Opened Mar 6, 2026 by zg-alexey Closed Mar 17, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
There is no 'About Codex' on windows
What subscription do you have?
Plus
What platform is your computer?
Microsoft Windows NT 10.0.19045.0 x64
What issue are you seeing?
When I exit Codex app on windows - there are still stale processes left I have to kill manually.
4 processes of Codex.exe, 1 - conhost.exe, 1 - wsl.exe
What steps can reproduce the bug?
Run Codex app on Win10 with WSL selected and exit it, check process manager.
What is the expected behavior?
_No response_
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I can confirm the same issue on Windows 10 with Codex version 26.305.950.0.
After closing Codex, related processes remain running.
With each new app launch, more processes are added, so the total count keeps growing over time.
These stale processes also keep consuming memory (in my case it grew significantly, up to around 2 GB total).
So this is reproducible for me on Windows 10 with v26.305.950.0 as well.
The just-received update 26.306.996.0 still has this issue.
Confirmed for me as well even without using WSL, 4 codex.exe processes, 1 conhost.exe process after closing each time.
Here's how it looks after opening and closing codex twice without taking any action inside codex:
<img width="1244" height="209" alt="Image" src="https://github.com/user-attachments/assets/c905a45c-9eaa-48cc-938b-07c68a8a2e27" />
Dup of #13970