Codex not showing diff

Open 💬 5 comments Opened Jul 24, 2026 by garzastrabajo
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.721.30844

What subscription do you have?

Plus

Which IDE are you using?

Vs code

What platform is your computer?

_No response_

What issue are you seeing?

I cant´t see the codex diff , i click the button "Review" to see what have changed but this "Oops, an error has occurred" appears in the screen whit a button with the text "try again" I click it and the window changes showing me in the screen "No diff available"

What steps can reproduce the bug?

.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #35058
  • #35076

Powered by Codex Action

tsampson · 1 month ago

I hit the same regression on Windows in VS Code.

Broken version:
openai.chatgpt@26.721.30844

Behavior:
Clicking the Codex Review button opens the “Codex Diff” tab, but the webview crashes with:
“Oops, an error has occurred. Try again.”

Repo state:
The underlying git diff is valid and small. VS Code Source Control diff works. The command-line git diff also works.

Workaround:
Downgrading the OpenAI/Codex VS Code extension to a build from about two weeks earlier immediately fixed the Review button. After downgrade, the same repository diff renders correctly.

This looks like a regression in the Codex Diff / Review webview in the newer extension build.

AndresArdeuz · 29 days ago

I can reproduce this on a newer extension build.

Environment:

  • OpenAI Codex extension: 26.721.41059 (openai.chatgpt, Linux x64 remote extension)
  • VS Code: 1.131.0
  • Local OS: Windows 11 x64
  • Workspace: VS Code Remote WSL, Debian

Minimal reproduction:

  1. Make a one-line comment-only change in README.md.
  2. Confirm git diff --check succeeds and VS Code's built-in Source Control diff renders correctly.
  3. Click the Codex Review button for the edit.

Observed behavior:

  • Initially the Codex Diff tab showed Oops, an error has occurred; retrying showed No diff available.
  • Reinstalling the extension and running Developer: Reload Window did not fix it.
  • The remote extension-host log also contained PendingMigrationError: navigator is now a global in nodejs, originating from openai.chatgpt-26.721.41059-linux-x64/out/extension.js.
  • Adding "extensions.supportNodeGlobalNavigator": true to the WSL machine settings removed PendingMigrationError after reload. The Codex Diff tab now goes directly to No diff available, but the underlying Codex renderer error remains.

Relevant Codex.log entry after the navigator error was eliminated:

[error] error boundary componentStack="... at R (.../webview/assets/editor-diff-page-DVdvmt2c.js:1:1030) at L (.../editor-diff-page-DVdvmt2c.js:1:643) ..." error={} name=AppRoutes

This appears isolated to the Codex Diff webview/route rather than Git or the workspace diff, since the same working-tree changes render normally in VS Code Source Control.

aliannas2 · 29 days ago

I hit the same Codex Diff failure in VS Code on macOS arm64.

Environment:

  • VS Code 1.131.0
  • Codex extension 26.721.41059

The Codex extension log showed an fs/readFile request failing with No such file or directory (os error 2), immediately followed by a React error boundary in editor-diff-page. The files shown in the inline diff still existed, and I had no chatgpt.cliExecutable override.

Working workaround:

  1. Open Extensions and select Codex.
  2. Gear menu -> Install Another Version.
  3. Install 26.715.61943.
  4. Run Developer: Reload Window.
  5. Temporarily disable auto-update for Codex.

The dedicated Codex Diff view works again after the downgrade, so this appears to be a regression in the 26.721 extension line. The inline diff and VS Code Source Control remain usable as fallbacks.

TitoCalleros · 14 days ago

I've just updated to the latest version, and the problem was solved