"Oops, an error has occurred" displayed after successful file editing tasks

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

• #22983
• #22996

Powered by Codex Action

Yes we are seeing this as well, reboots and works for 5-10 minutes then gets the error again, was after update

<img width="1431" height="818" alt="Image" src="https://github.com/user-attachments/assets/83027ce9-eb80-439f-99db-aa26c1333189" />

<img width="770" height="392" alt="Image" src="https://github.com/user-attachments/assets/a6deb810-db81-44c2-8195-eff99905fc4e" />

It seems that long session (mine is about 3MB with 1061 JSONL records with one very long record over 100k characters) will have this issue. Very inconvenient and frustrating.

Same issue here on Windows 11 with Codex Desktop 26.513.31313.

Symptoms:

• Existing conversations fail with “Oops, an error has occurred”
• Creating a new conversation also fails
• Clearing app cache/auth and reinstalling did not fix it
• Codex CLI still works

I backed up %USERPROFILE%\.codex and tried repairing session JSONL files containing rendered git directives with Windows backslash paths. The issue still persists / improved partially.

This looks related to #22984, #22977, #22985, and #22973.

In codex I've done a feedback its saying to mention a feedback id for openai on github: 019e2f8b-1e19-7891-9333-9641d7c298b7 , hopefully they will have a fix in place soon.

Same issue here on Windows 11 with Codex Desktop 26.513.31313. Symptoms: Existing conversations fail with “Oops, an error has occurred” Creating a new conversation also fails Clearing app cache/auth and reinstalling did not fix it Codex CLI still works I backed up %USERPROFILE%\.codex and tried repairing session JSONL files containing rendered git directives with Windows backslash paths. The issue still persists / improved partially. This looks related to #22984, #22977, #22985, and #22973.

Thank you! Have to use Codex CLI for now, although I prefer the Codex App 👍

Same issue here, reported in Codex app under 019e30bb-006b-7fb3-a19f-c8fcf5f89daf

same here, super annoying i was trying to uninstall and install, does not work at all

same. 019e3064-3e83-7df3-9195-30c3966dcd32 I noticed that everything works fine in the VSCode extension though; it's just the Codex app.

Would this bug happen on new threads at any point? Like after doing git commits, etc?

Yes, it could happen in new threads, but only under the same trigger.

From what we found, the risky case is not “doing a git commit” by itself. The risky case is a saved assistant message containing Codex app git directives like:

::git-commit{cwd="D:\...\repo"}
::git-stage{cwd="D:\...\repo"}
::git-create-branch{cwd="D:\...\repo" branch="..."}

So a new thread could become affected after Codex performs git actions and writes those app directives into the final response using Windows backslash paths. It may render fine initially, then fail when reopened because the renderer reparses the saved message.

Safer until the app is fixed:

• Avoid having Codex perform branch/stage/commit/push/PR actions in-app if you need the thread to reopen reliably.
• If Codex does perform git actions, using forward-slash paths like D:/.../... in any app directive would likely avoid this specific parser failure.
• Regular terminal git commands you run yourself are not the issue unless the thread stores one of those ::git-* directives afterward.

So: yes, new threads can hit it, but only if the same malformed saved directive gets written into the conversation.

Same issue, after about 5 prompts it gives "Oops, an error has occurred" and the chat becomes completely inaccessible

same for me, previous version had no issues but can't revert

Having this same issue after updating to the latest version earlier this morning.

cant get anything done today ~~~

We are working on a hotfix for this issue.

We are working on a hotfix for this issue.

Thanks, it is truly urgent 🙏

We've uploaded the update to the Windows store, so it should be available shortly. I'd appreciate it if someone could confirm when it's available that it has addressed the problem.

We've uploaded the update to the Windows store, so it should be available shortly. I'd appreciate it if someone could confirm when it's available that it has addressed the problem.

I'll respond here once the update is available to me. Thanks!

I was able to pull down the new update on the windows store problem seems to have gone away and my session chats are back.

Just downloaded the hotfix, and things seem to be working normally for me again!

downloaded the hotfix, its working for me now as well

We've uploaded the update to the Windows store, so it should be available shortly. I'd appreciate it if someone could confirm when it's available that it has addressed the problem.

It wasn't working for me initially, but after uninstalling, restarting my PC, and reinstalling, it's working perfectly. I can now open the sessions that were failing before. Thanks so much! I hadn't been able to use Codex for about 8 hours.

We've uploaded the update to the Windows store, so it should be available shortly. I'd appreciate it if someone could confirm when it's available that it has addressed the problem.

Installed the update and the problem was effectively solved, thanks!

Thanks for confirming that the fix works.