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

Open
#33,629 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
vscode
Domain
developer-experience

Research direction

Start by reproducing the VS Code extension flow in a Git repository on the reported Windows environment: apply Codex changes, then use the revert action and inspect why the listed file is skipped. Trace the revert entry point and its handling of unavailable, moved, or conflicting files. Done means changed files are restored or each skipped file reports a specific reason.

Written by the indexing model from the issue text.

Description

bug extension windows-os
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

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.