Changes Aborted Hides Suggested Changes from View
Resolved 💬 5 comments Opened Mar 5, 2026 by craigmorissette Closed Apr 11, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Why oh why does codex hide it's changes it preposes to the user EVERYTIME after I say, no--I want more information to validate whether or not I want this for my project?
The change diff should stay up in view--NOT dispose/hide. Anyone else find this extremely frustrating? I can read what it wants to do, which is great, but often I need clarification about how this will effect the rest of the project.
Isn't this a no brainer?
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Can you provide more details? Which variant of Codex are you using? Which version? Which platform?
When you say that you're "saying no", are you referring to plan mode choices?
Is this a feature request? A bug report? What are the repro steps?
0.107.0 macOS on Ghostty, zsh
I'm talking about given the 3 options to approve the code changes:
Runs just that one requested command.
Approves this command pattern going forward (for example a prefix
like git push), so I won’t need to ask each time.
Command doesn’t run.
This is a feature request, change of codex default behaviour. Steps to reproduce are: Ask it to design software.
This is a cli problem
This feature request hasn't received enough upvotes, so I'm going to close it.