VS Code extension fails to revert Codex changes and reports files as skipped

Open 💬 0 comments Opened Jul 16, 2026 by HeyrbiarKhan

What version of the IDE extension are you using?

v26.707.91948

What subscription do you have?

Pro

Which IDE are you using?

VS Code

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The Codex extension in VS Code is unable to revert changes it previously made.

Whenever I click the option to revert Codex's changes, I receive the following message:

No changes reverted There were issues reverting some files Skipped (1)

Example skipped file:

tests/e2e/administration/user-management.spec.js

The affected filename varies depending on which file Codex modified. This happens repeatedly, and the extension does not explain why the file was skipped.

What steps can reproduce the bug?

  1. Open a Git repository in VS Code.
  2. Use the Codex extension to make changes to one or more files.
  3. Allow Codex to apply the changes.
  4. Use the Codex UI to revert the changes.
  5. Observe that no changes are reverted and one or more files are listed as skipped.

The issue occurs consistently for me, although the skipped filename changes depending on the files modified by Codex.

What is the expected behavior?

The Codex extension should restore every file it changed to its exact state before the Codex changes were applied.

If a file cannot be reverted, the extension should provide a specific reason, such as:

  • the file was modified after Codex applied its changes
  • the file was renamed, deleted, or moved
  • the working tree contains conflicting changes
  • the original file state is unavailable

Additional information

_No response_

View original on GitHub ↗