Either pressing X on the top right or Alt-F4 still leaves it running with severak codex.exe instances. Please provide a way to properly exit the application.
2 Likes
That’s odd. Closing the app should fully exit it.
I tried reproducing this on my end, and when I close Codex, it no longer shows up in Task Manager. While it’s running, I do see a few subprocesses grouped under the main Codex process, which is expected behavior.
In your case, are the multiple codex.exe entries showing as subprocesses under a single main process, or are they appearing as completely separate processes?
If they’re separate and persist even after closing the app, this might be account or environment specific. In that case, it’s best to reach out to support@openai.com so the team can take a closer look with logs.
1 Like
Same thing on my end. Multiple codex instances are lingering after closing the app (either by pressing X or Alt-F4) with no processor use.
Something similar happened to me before when I had Codex start servers and Playwright instances. The agent completed the task and reported back, but the processes were never stopped.
Maybe these cases are somewhat similar?
I was able to reduce the issue by adding cleanup instructions in the part of the project where they made the most sense.
1 Like
That’s probably doable, but the app should do this. Not the cleanup instructions.
1 Like
I completely agree. After a session that ran for several days, I ended up with more than 100 orphaned processes. It is pretty wild, even if it does not matter that much in the end.