Codex exits while processing a prompt taking credits away without doing the work
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.707.62119
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows 11 25H2 26200.8655
What issue are you seeing?
019f55fe-8519-7a50-af32-ccc4b7b49713
I'm using codex to write python and process data within a SQL database via docker desktop so its a local SQL. But when i run a prompt that takes longer than 5 minutes the codex desktop app randomly exits and totally forgets the prompt and the chat, doesn't provide any of the work yet it takes all of the credit for doing it. Its Monday and i have almost run through a weeks worth of Codex credit just re-running Prompts because Codex has exited and taken the credit.
What steps can reproduce the bug?
Hard to reproduce since all evidence is lost when codex exits. I get no error message or sound notification Codex just vanishes and shuts down completely even from the system tray.
What is the expected behavior?
I expect it to finish processing my prompt, or at least not charge me for work it hasn't done.
Additional information
I should not be paying in codex time for prompts that have not been processed or having to rerun prompts costing 2X or 3X the codex usage time because the system has not processed them. This has already cost me more than 50% my weekly amount and its only Monday.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I looked at the potential duplicates and neither of them match, one is saying it crashes even if a simple Hello is typed in and the other states that a windows crash dump was created, I have neither of these, Codex version 26.707.62119 seems to just vanish while processing a prompt sometimes it can be 2 minutes others it can be 20 minutes into the routine but every time there is no warning, no error message, no crash dump or error log in windows its just gone. then when i start codex up again all i see is the previous reply with my last prompt missing and no reply but it still consumes all the codex usage time.
I have to verify anything that has been changed and do a git diff --check then do a prompt to codex to verify what was changed eating more codex time before running the entire prompt again to make the changes costing 2X or 3X the amount of codex usage as it would of if it had run properly.