Unable to Revert Changes in VS Code Codex Extension
OpenAI Developer Community
June 5, 2026
Welcome to the forum!
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex.
I had ChatGPT look for the closest related issue and it identified:
github.com/openai/codex
Bug report: VSCode extension failed to revert the changes
opened 01:38PM - 25 Nov 25 UTC
kaizhuanren
bug extension
What version of the VS Code extension are you using? 0.4.46 ### What subsc…ription do you have? bussiness ### Which IDE are you using? vscode ### What platform is your computer? Darwin 25.1.0 arm64 arm ### What issue are you seeing? Environment: macOS, VSCode extension 0.4.46. Codex deleted parts of my code unexpectedly. When I clicked the Revert changes button in the VSCode extension, it showed “Failed to revert changes.” The history changes panel did not correctly display the deleted parts, although the conversation’s history of changes did show them. I had to manually copy and paste from the conversation history to avoid losing uncommitted code. The revert button in the VSCode extension does not work properly and needs to be fixed. I also suggest adding an option or prompt to automatically create a commit before Codex starts editing, so it is easier to restore previous versions. ### What steps can reproduce the bug? I asked Codex to find duplicate parts in the code and delete them, but Codex mistakenly started truncating the file from an incorrect location, causing the file to be cut off and a large amount of code after that point to be lost. When I clicked the revert button (↩️), it showed “failed to revert the changes.” ### What is the expected behavior? No response ### Additional information No response
If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
Discussion in the ATmosphere