Existing session fails to load, and tasks in both new and existing sessions eventually time out #40183

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.41509

What subscription do you have?

ChatGPT PRO

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

An existing Codex session that I was actively using only a few hours ago no longer loads its conversation history.

The session itself still appears normally in the Codex App, including its title. However, when I open it, the conversation area remains completely blank with the Codex logo/loading state in the center. The previous messages and session content never appear.

In addition, this does not appear to be limited to loading the existing session history.

If I enter a new task in either:

• a newly created session, or
• an existing session that I can access,

the task does not complete and eventually results in a timeout.

There is therefore currently no reliable way for me to use Codex: some existing session histories fail to load, while task execution in both new and existing sessions eventually times out.

What steps can reproduce the bug?

1. Open the Codex App on macOS.
2. Select an existing session that was working normally only a few hours earlier.
3. The session title loads correctly, but the main conversation area remains blank.
4. Previous messages and conversation history do not load, even after waiting.
5. Create a new session and enter a task.
6. The task fails to complete and eventually times out.
7. Enter a task in another existing/accessible session.
8. The same timeout behavior occurs.

This has happened to me before as well. On the previous occurrence, the affected session eventually became accessible again without me modifying or deleting any local Codex data.

The issue therefore appears to be intermittent.

What is the expected behavior?

Existing sessions should restore and display their previous conversation history normally.

Tasks submitted in both new and existing sessions should start and complete normally without timing out.

If there is a temporary connectivity or backend issue, the app should surface a meaningful error rather than leaving an existing session indefinitely blank or allowing a task to run until it eventually times out.

Additional information

This is not the first time I have experienced a similar session-loading issue.

A previous session became temporarily inaccessible in the same way and later recovered on its own. This suggests that the underlying session data may still exist, but the Codex App is intermittently failing to retrieve, restore, or render the conversation history.

However, during the current occurrence, task execution is also affected: tasks submitted in both newly created sessions and existing sessions eventually time out.

Because the timeout occurs across multiple sessions, including newly created ones, this may not be isolated to a single corrupted session.

The currently affected session was actively used only a few hours before the problem appeared.

I have attached a screenshot showing one affected session. The session title is visible at the top, while the entire conversation area remains blank.

I have intentionally not deleted or modified any local Codex session/cache data so that the affected state can be preserved for debugging if needed.