After waiting for me, every new message results in "Error creating chat failed to start turn: internal error; agent loop died unexpectedly" and "Error submitting message"

[NichUK]

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

26.715.72359

What subscription do you have?

Pro

What platform is your computer?

Windows 11

What issue are you seeing?

Sometimes, after Codex waits for me to interact, and if I don't, when I finally come back to the chat, Codex will throw a red toast at the top of the app saying

Error creating chat
failed to start turn: internal error; agent loop died unexpectedly

and then "Error submitting message" in the chat.

This will repeat for every message in the chat until the app is restarted.

Other chats continue to work, but then sometimes develop the same problem.

What steps can reproduce the bug?

It seems to happen when a chat requests an interactive response, and I don't provide that within some unknown amount of time, but I can't reproduce it reliably.

What is the expected behavior?

Chats should never produce an internal error.

Additional information

No response

[github-actions]

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

• Codex Desktop: thread/resume can return a thread while Shutdown is pending, leaving a dead agent loop #33957
• Codex view resumes a task while its agent loop is shutting down, leaving the task unusable #34131

Powered by Codex Action

[GalaxyRuler]

Additional Windows desktop report for this same failure:

• Desktop package version: OpenAI.Codex 26.721.4979.0.
• User-observed trigger: every time the agent attempts to use Codex's built-in Browser tool, Codex subsequently crashes or the agent loop dies.
• The UI then shows: failed to start turn: internal error: agent loop died unexpectedly, followed by message-submission errors.
• A full quit and relaunch is the only observed recovery; the app works again temporarily after restarting.
• Local Codex desktop logs recorded the exact failure at 2026-07-26 08:12-08:14 UTC (11:12-11:14 Asia/Riyadh).
• Immediate diagnostic context did not show OOM, panic, network, or process-termination markers, and the machine had approximately 42 GB RAM free when checked.

Expected behavior: invoking the built-in Browser should either succeed or fail recoverably without leaving the agent loop unable to create further turns.

No logs are attached because the desktop logs may contain prompt/project content.