Codex crashes itself during running without showing the session id to resume
Resolved 💬 3 comments Opened Nov 28, 2025 by BrianLeeB Closed Nov 30, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.63.0
What subscription do you have?
pro
Which model were you using?
gpt-5.1-codex-high
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
I opened about 5+ codex sessions at the same time, and four of them randomly and suddenly crash themselves without showing the session id to resume. An example situation is as follows:
<img width="1009" height="119" alt="Image" src="https://github.com/user-attachments/assets/637dd645-eb56-4d13-810c-16127a8ce8b3" />
I just went back to my terminal after it crashed itself.
What steps can reproduce the bug?
session id 019acb1f-f611-72d3-b805-90f39002764c
Token usage: total=669,756 input=664,247 (+ 138,112 cached) output=5,509 (reasoning 3,200)
What is the expected behavior?
_No response_
Additional information
_No response_
3 Comments
To add the information above, I have tested with different internet connection. It should not be the issue with my network.
I'm using warp. not sure if this is the reason, i'm testing it.
You say that codex crashed. What error message are you seeing that leads you to believe that codex is crashing?
Thanks for posting the session ID, but it appears that you haven't used the
/feedbacktool to upload your session. Could you resume that session and upload it using/feedback? If that session is no longer available and you're able to reproduce this problem, it's fine to upload a different session and provide its thread ID.Hi Eric,
Thanks for your willingness to help! I don't see any error message when it crashed. I have tested it over the weekend. Now I believe it's because of the terminal app I'm using. When i reduce the number of concurrent sessions, the crashing never happened again.
Best,
Brian