Prompt to save file before Codex applies edits to unsaved files with changes
Resolved 💬 5 comments Opened Sep 18, 2025 by adamdry Closed Dec 18, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What feature would you like to see?
If Codex wants to edit a file that has outstanding changes in it, it would be great if it prompted you to save the file before it made its own changes. Otherwise you have to perform a diff which is painful. I find I'm doing this often and it's the biggest gripe I have with Codex so far.
It's otherwise very impressive and useful!
Are you interested in implementing this feature?
_No response_
Additional information
_No response_
5 Comments
You can do this with the
notifyhook. Have itgit committhe change after it's done changing it.@nicholaswmin thanks for the response but I'm not looking to create a git commit, I just haven't saved the file in vs code to disk yet.
Having typed this out I realised I can just set auto save to onFocusChange in my vscode settings - which does the job for me!
Thanks for taking the time to respond, you got me on the right thought path 😄
Well it could be whatever :) no problem
This feature request hasn't received any new upvotes or posts in a long time, so I'm going to close it out.
Shame that it's closed but want to say I've also had this frustration! Could even be a prompt that comes up before the prompt begins processing that just highlights if you have any unsaved changes