Did you remove the undo feature? If I say undo something, why would I ever want this to blindly checkout the file from git?
Resolved 💬 7 comments Opened Jan 23, 2026 by rlewkowicz Closed Jan 23, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.89.0
What subscription do you have?
pro
Which model were you using?
5.2 max
What platform is your computer?
Linux
What terminal emulator and version are you using (if applicable)?
n/a
What issue are you seeing?
I might be crazy, but this had an undo feature for a small time and would do snapshots?
Generally, if I say "undo that" it should not just blindly checkout files. I REEEEEEALLLY hate that. So if I did not do a commit, and was in the middle of work start a new session and it foobars, it will just checkout what ever was last in git. Could be hours of work, could be hundreds of prompts and it blindly checks the file out. I thought yall had fixed that. Crazy.
What steps can reproduce the bug?
Tell it to undo something
What is the expected behavior?
It undoes the last change, not randomly checks out the file. I used to guard against this, but it seemed fixed for a while.
Additional information
_No response_
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Yes, this feature was removed. It was not seeing much usage, and its implementation was causing problems for many users — even those who were not using it.
If we decide to bring back this functionality at some point, it will require a new design.
If you'd like to see something like this implemented, please upvote #9203.
@etraut-openai if there could at least be some guard against that, that would be cool. I know these are all fuzzy. It feels broadly regressed. Less autonomous. Lots of goofy like path on path appending etc. I know these are not deterministic, it just feels way more goofy recently.
@rlewkowicz, this is model behavior — something that's not under the control of the Codex harness. If you see undesirable model behavior, the best way to report that is through the use of the
/feedbackslash command, which will allow you to upload your session details. Our colleagues who are responsible for training the codex models use this data to help inform improvements for the next-generation models.The undo function is meant to compensate for the errors the AI makes, and it’s still retained in Cursor and even other editors—it’s an incredibly practical feature. I really can’t wrap my head around why it was removed. Does everyone actually think the AI’s generated output is always flawless and never makes mistakes?
@RobRoyce, appreciate the feedback, but you're being kind of obnoxious. Please be respectful with your comments.
@etraut-openai I lost time and money because of this issue, and I am a bit annoyed myself. But you're right, apologies. I will delete my comments.