Codex should "see" cancelled commands
Resolved 💬 3 comments Opened Oct 13, 2025 by josephrocca Closed Jan 10, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
0.46.0
What steps can reproduce the bug?
- Codex does something stupid
- You cancel the command and say "No, don't do that, it's stupid"
- Codex says "I didn't do that, what are you talking about"
- You realize that Codex can't see actions it took if they were cancelled
In my case it kept trying to run a script (written on the fly with python -c "...") that was taking too long. But every time I canceled it it wouldn't know what it had just done, so I couldn't say "Don't do what you just did, try something else".
Here's another example (not me) of why the current behavior should be considered a bug:
(I'm not referrring to the rm -rf, I'm referrring to the "denial" - it literally can't see what it tried to do, so it's actually being honest.)
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is a frequent occurrence. Whenever I have a bug in tests that makes them hang, I need to manually stop the test and codex is confused about what happened.
Closing old issue.