Changes Aborted Hides Suggested Changes from View
Resolved 💬 5 comments Opened Mar 5, 2026 by craigmorissette Closed Apr 11, 2026
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?
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗