[Bug] codex process is killed suddenly on macOS with no error, crash report or logs
Open 💬 2 comments Opened Mar 2, 2026 by vanhiepdam
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.106.0
What subscription do you have?
Using Azure OpenAI token
Which model were you using?
gpt-5, gpt-5.2-codex, gpt-5.3-codex
What platform is your computer?
Darwin 24.5.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
Pycharm Terminal
What issue are you seeing?
The codex binary/process is being terminated abruptly while running normally on macOS.
There is no crash report, no stack trace, no error message, and no entry in Console.app (other than the minimal kill line).The only visible information is:
63052 killed codex
What steps can reproduce the bug?
codex (however you normally start it — CLI, script, etc.)
Let it run (it works for a while)
Process disappears without warning
What is the expected behavior?
no error
Additional information
_No response_
2 Comments
the issue never occurred in my older version. 0.64.1. it always occur if I had a long running request
Thanks for the report.
killed codexlooks like a shell-generated message, not a Codex error line: it means the top-levelcodexprocess died from SIGKILL.The Codex CLI doesn't SIGKILL itself, so this is almost definitely an external kill. Given that it happens on long-running requests and not in 0.64.x, the leading guess is resource pressure on macOS, with PyCharm Terminal or security tooling as other possibilities.
I recommend trying the same workflow outside PyCharm (Terminal.app or iTerm).