Codex resume does not show the id in 0.121
Resolved 💬 4 comments Opened Apr 17, 2026 by matssk Closed Apr 20, 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.121
What subscription do you have?
Pro
Which model were you using?
_No response_
What platform is your computer?
_No response_
What terminal emulator and version are you using (if applicable)?
VSCode
What issue are you seeing?
If I write /fork or press ctrl+c, it now often displays the following message
To continue this session, run codex resume 'Review the current code changes (staged, unstaged, and
untracked files) and provide prioritized findings.' instead of codex resume 'some-id-here-'
What steps can reproduce the bug?
I'm not really sure. It happens only sometimes in long sessions, when pressing ctrl+c or typing /fork.
What is the expected behavior?
_No response_
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
No, these are not the same issue. In this issue what happens is that it sometimes prints the review prompt in place of the session id.
I think it may be something vscode specific and related to other rendering issues. It happens after text gets cutoff in the vscode terminal. So codex finished some task, but the last text gets cut off and then when clicking ctrl+c this happens.
Thanks for the bug report. This will be addressed in the next release.