You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
github-actions commentedon Mar 6, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
swebdevelopers commentedon Mar 7, 2026
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.
bLightZP commentedon Mar 8, 2026
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:

etraut-openai commentedon Mar 17, 2026
Dup of #13970