›_ Codex Issues
Codex Issues / #35227

Popup "Oops, an error has occurred"

Open 💬 4 comments Opened Jul 24, 2026 by Cazorlas
💡 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?

26.721.30844

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?

My codex show "Oops, an error has occurred" and I can not process.

What steps can reproduce the bug?

Just open codex on VS code

What is the expected behavior?

<img width="535" height="321" alt="Image" src="https://github.com/user-attachments/assets/803d3595-912a-4ce9-904c-0aae547a92a2" />

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 1 month ago

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

  • #35208

Powered by Codex Action

Jomo178 · 1 month ago

I have the exact same issue.

txtad · 28 days ago

This issue also reproduces on Linux when opening the Codex Diff editor.

Steps to reproduce

  1. Have Codex make one or more code changes.
  2. Wait for Codex to display the changed-file summary.
  3. Click Review next to any changed file.
  4. The Codex Diff editor opens but displays:

> Oops, an error has occurred

This reproduces consistently for every changed file I have tested. The affected files open normally in the standard VS Code editor.

I have reproduced the same failure on two separate workstations, both running Linux Mint.

Environment

Codex extension: 26.5721.30844

Distribution: Linux Mint 22.3

Version: 1.131.0
Commit: e4c7e7b1d6d060162f4aa7f8225271b67ce1df75
Date: 2026-07-28T10:51:25Z
Electron: 42.7.0
ElectronBuildId: 14710161
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Linux x64 7.0.0-28-generic

Because this reproduces on Linux, the issue does not appear to be Windows-specific.

txtad · 28 days ago

Because this reproduces on two Linux Mint workstations, the issue does not appear to be Windows-specific. The windows-os label may need to be removed or supplemented with the applicable Linux label.