/resume stopped working, codex freeze on it
Resolved 💬 4 comments Opened Feb 18, 2026 by tprochazka Closed Feb 18, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.103.0
What subscription do you have?
Enterprise
Which model were you using?
gpt-5.3-codex
What platform is your computer?
Windows 11
What terminal emulator and version are you using (if applicable)?
PowerShell 7, CMD (all terminals the same)
What issue are you seeing?
/resume stopped working, codex freeze on that, no response, esc, ctrl + c nothing reacts, it stays like that forever
<img width="966" height="633" alt="Image" src="https://github.com/user-attachments/assets/6aa04433-d937-4fb9-862d-ae86ffd6aae3" />
It is happening for all projects, no one works, all sessions are lost.
What steps can reproduce the bug?
Just call /resume
What is the expected behavior?
To list all the sessions, it was working just an hour ago.
Corrupted history?
Is there any tool to check and fix history/session integrity?
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
It is happening even for a new folder. I open the codex CLI in a folder that was never used. Here should be really no history, but /resume anyway freeze, it is not possible to leave it.
I also tried to use a new folder, run Codex, do some job, end it, run again, and resume, nothing.
Do you suspect that this is a regression in the client? Does the problem go away if you downgrade to an earlier version? If so, which version does it start occurring?
I gave it some time, restarted the computer, and now it's working again. Is it possible that there was one stuck client that blocked access to session history files? Anyway, we can close probably. I will see if it happens again.