Leaky /undo
Resolved 💬 2 comments Opened Dec 16, 2025 by Nikaaner Closed Jan 6, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.73.0
What subscription do you have?
Plus
Which model were you using?
gpt-5.1-codex-max (reasoning high, summaries auto)
What platform is your computer?
macOS
What issue are you seeing?
I interrupted the implementation using Esc, did /undo, and re-entered the question. The answer included data from the interrupted and undone implementation (i.e., the parameters that were added there).
What steps can reproduce the bug?
Uploaded thread: 019b281b-18a2-7511-b330-21804853a4f5
What is the expected behavior?
The implementation that was undone should have been forgotten.
Additional information
_No response_
2 Comments
The
/undoslash command doesn't exist anymore: https://github.com/openai/codex/pull/8424. But I don't understand this move. Why remove/undo? @jif-oaiWe've decided to remove the
/undofunctionality. It was not getting much usage, and the implementation was causing a number of problems — even for users who didn't use it. If you have a need for this feature, consider opening a new feature request (or search for an existing one if you're not the first to come across this comment) and describe your use case and desired behavior.