Codex tends to commit suicide
Open 💬 0 comments Opened Feb 24, 2026 by JKamsker
What issue are you seeing?
Often, when codex starts another child codex process, it gets impatient quickly and wants to kill "orphaned sessions".
Ideally this would be solved by telling codex(in its default context) to be careful with killing codex processes and never killing more than one, and only when its confident which processes to kill.
What steps can reproduce the bug?
Tell it to run a review using "codex exec review"
What is the expected behavior?
Not kill itself and all the other sessions unexpectly.
Additional information
_No response_