Viewing images causes sessions to be stuck in a Reconnecting loop #32394

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

26.707.41301

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

For the past 24 hours, Codex desktop has failed almost every time it needs to analyse an image. It usually thinks for 7+ minutes before becoming stuck in a “Reconnecting” loop, which comes with the following error message:

stream disconnected before completion: websocket closed by server before response.completed

Across dozens of attempts, only two completed successfully.

This occurs across both Sol and Terra, at multiple reasoning levels. It does not require a long-running conversation, large context, multiple images, or a high-resolution image. It can happen from a brand-new chat with a single prompt and a single low-resolution image.

It also happens whether the image is attached directly or the agent is instructed to inspect an image stored locally, such as a file on the Desktop.

Edit: To clarify, this is not limited to single-message threads. A session can be working normally until the agent attempts to inspect an image. At that point, it enters the reconnect loop, and every subsequent message in that session does the same. The session is effectively bricked from that point onward.

This makes image-heavy web design work extremely difficult and forces me to use browser-based workflows for tasks where browser use would otherwise be unnecessary, causing slower workflows and avoidable token usage.

What steps can reproduce the bug?

1. Open a new chat in the Codex desktop app.
2. Select Sol or Terra at any reasoning level.
3. Either:
   • Attach a single low-resolution image, or
   • Ask the agent to inspect an image stored locally, such as one on the Desktop.
4. Ask a simple question requiring the image to be analysed.
5. Wait several minutes.

In most attempts, the agent continues thinking for 7+ minutes and then enters a repeating “Reconnecting” state without completing the response.

What is the expected behavior?

Codex should analyse a single attached or local image and return a response within a reasonable amount of time, without entering a reconnect loop.

Additional information

This has been happening consistently for approximately 24 hours. Out of dozens of attempts during that period, only two image-analysis requests completed successfully.

It appears unrelated to conversation length, context-window usage, image count, or image resolution.