Oops, an error has occurred

Resolved 💬 13 comments Opened May 16, 2026 by vannylyvan0209-hub Closed May 16, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Oops, an error has occurred
Check for updates
Try again

<img width="1067" height="616" alt="Image" src="https://github.com/user-attachments/assets/4c03bb98-91b5-4e7d-a919-3f8172f2fc58" />

View original on GitHub ↗

13 Comments

github-actions[bot] contributor · 2 months ago

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

  • #22977
  • #22963
  • #22973
  • #22962
  • #22956

Powered by Codex Action

7000x · 2 months ago

一样,今天更新后出现的问题

itstheceo · 2 months ago

I am getting this with the latest update. Whenever I navigate away from a session (chat) and back again, it shows me the "Oops, an error has occured".

Prior to that, Codex itself was able to resume (I provded Session ID). Codex says the state on disk is fine, and it's likely a UI bug.

This is pretty annoying, I will revert to using the CLI for now.

kraybit · 2 months ago

Tried removing the entire .codex folder and start over. This still happens.

  • It happens with a single chat session. (I never "clicked away" from it.)
  • It seems to happen the moment the Agent has finished a commit, and is about to display the summary message? (Not sure)
kraybit · 2 months ago

This message crashes the Chat Session with "Oops, an error has occurred":

{"timestamp":"2026-05-16T10:02:39.365Z","type":"event_msg","payload":{"type":"agent_message","message":"Hi\n\n::git-commit{cwd=\"C:\\Users\\MyName\\MyProject\"}","phase":"final_answer","memory_citation":null}}
  • This message is last in the session
  • The path C:\Users\MyName\MyProject is valid. That's where we've been working.

This altered message does _not_ crash the session: (I removed the ::git-commit part, restarted Codex.)

{"timestamp":"2026-05-16T10:02:39.365Z","type":"event_msg","payload":{"type":"agent_message","message":"Hi","phase":"final_answer","memory_citation":null}}

It seems the ::git-commit part crashes the chat?

kraybit · 2 months ago

Workaround

This seems to work: (Say at beginning of session)

When you write a summary you have this ::git-commit part? With the current version of Codex, that seems to crash the chat rendering. Could you skip those parts for the remainder of this session?

GPT seems to revert to displaying commit info in plain text (which works fine).

aidandavis · 2 months ago

Seeing this too. Windows 11, once it errors then all chats/sessions will error and the execution stops. Cannot recover any sessions.

onlyluck77 · 2 months ago

Same issue here. A my previous sessions have this problem. I was able to start a new task, but once it completed this message came up. Windows 11.

<img width="501" height="283" alt="Image" src="https://github.com/user-attachments/assets/6ac29506-499a-483e-bbb7-ee3e57fffa86" />

<img width="280" height="121" alt="Image" src="https://github.com/user-attachments/assets/1f5f0bbc-596e-4e3d-ab03-548465cd102c" />

vannylyvan0209-hub · 2 months ago

just update, it solve guys

etraut-openai contributor · 2 months ago

We've issued a hotfix to address this. Please update to the latest version.

vannylyvan0209-hub · 2 months ago

When swiching the account
the codex can't load the chat

stuck at blinking and loading state

we have to exit or force close by end tank and reopen to be able to continue the chat

vannylyvan0209-hub · 2 months ago

When swiching the account
the codex can't load the chat

stuck at blinking and loading state

we have to exit or force close by end tank and reopen to be able to continue the chat

<img width="1347" height="1003" alt="Image" src="https://github.com/user-attachments/assets/0c50ee96-5c06-4438-b755-5c686273903b" />

etraut-openai contributor · 2 months ago

This issue was fixed in the latest update. If you're seeing an `"Oops, an error has occurred" message with the latest version, then it's a different issue. Please open a new bug report in that case.

I'm going to lock this issue as resolved.