Skip to content

Frequent reconnect loop in Codex App: websocket closed by server before response.completed #18960

Description

@GGBondBlueWhale

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

26.417.41555 (1858)

What subscription do you have?

Pro

What platform is your computer?

macOS

What issue are you seeing?

Over the past few hours, I have repeatedly hit a streaming failure in the Codex App during normal use.

While a response is streaming, the app starts reconnecting multiple times and then fails with:

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

The reconnect sequence I saw included:

  • Reconnecting... 2/5
  • Reconnecting... 3/5
  • Reconnecting... 4/5
  • Reconnecting... 5/5

This has happened many times within a few hours and makes the app feel noticeably slow and unreliable.

What steps can reproduce the bug?

I do not have a fully deterministic repro yet, but this is the pattern I have observed:

  1. Use the Codex App normally for some time
  2. Send a prompt that produces a streamed response
  3. During streaming, the connection drops unexpectedly
  4. The app shows repeated reconnect attempts
  5. The turn fails before response.completed

This happened multiple times over the last few hours during normal usage.

What is the expected behavior?

The stream should stay connected until the response is fully completed, or the app should recover transparently without losing the response.

Additional information

  • The failure appears intermittent, but frequent enough to significantly interrupt normal workflow
  • When it happens, I often have to retry or regenerate
  • I have a screenshot showing the reconnect loop and exact error text if needed
  • I also encountered the Reconnecting... problem multiple times within the same task, not just across separate tasks
  • Based on when I started noticing it, this appears to have been happening since around 1–2 AM US Eastern Time
  • I am reasonably confident this was not caused by my local network, because my internet connection remained stable and usable throughout the same period
  • During this same window, Codex also felt unusually slow overall, even when using GPT-5.4 in fast mode
Image Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingconnectivityIssues involving networking or endpoint connectivity problems (disconnections)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions