Codex frequently requires restoring the network connection after almost every prompt

Open 💬 3 comments Opened Jul 13, 2026 by EarFrog
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Description

The Codex desktop app frequently loses its network connection and requires the connection to be restored before it can continue. This happens after almost every prompt and severely disrupts the user experience.

Steps to reproduce

  1. Open the Codex desktop app.
  2. Start or continue a task.
  3. Send a prompt.
  4. Observe that Codex asks to restore the network connection.
  5. Restore the connection and send another prompt.
  6. The same problem occurs again.

Expected behavior

The network connection should remain stable across prompts without requiring manual recovery.

Actual behavior

Almost every prompt is interrupted by a request to restore the network connection.

Frequency and impact

This occurs almost every time a prompt is sent and makes Codex very difficult to use.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 1 month ago

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

  • #32365

Powered by Codex Action

iAchilles · 1 month ago

faced with the same issue after update app.

Moncefmd · 1 month ago

Canadian here. I am encountering very frequently the same issue. This was happening to me since quite some time though (more than a few weeks ago, I found that it happens in threads that contain lots of images.

I tried to diagnose networking through sol max, and it could not find anything. The only advice was to send /feedback. Other than that, what helps a lot is to start a new thread. Then it becomes good again for a few prompts, but as soon as the number of images in the thread becomes big (even by just viewing 20 images or so and generating a few), the connection problems become unbearable.