Skip to content

Codex session repeatedly disconnects: websocket closed before response.completed #24533

Open
Open
Codex session repeatedly disconnects: websocket closed before response.completed#24533
Labels
appIssues related to the Codex desktop appbugSomething isn't workingconnectivityIssues involving networking or endpoint connectivity problems (disconnections)

Description

@GGBondBlueWhale
GGBondBlueWhale
opened on May 26, 2026

Summary

While running a Codex task, the connection became very unstable and repeatedly showed reconnecting behavior. The session eventually surfaced this error:

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

The UI showed reconnect attempts such as Reconnecting... 2/5 during the task.

Feedback ID

019e62a9-9544-7780-864a-566226a188ac

Environment

  • Codex app version: 26.519.41501 (3044)
  • macOS: Tahoe 26.5
  • Device: MacBook Pro 16-inch, Apple M5 Max, 128 GB memory
  • Network: home network, no VPN enabled

Expected behavior

Codex should keep the session stream stable until the task completes, or recover cleanly after a transient reconnect without losing the response/completion state.

Actual behavior

The stream disconnected before completion and the websocket was closed by the server before response.completed, causing the task to become unstable instead of finishing normally.

Image

Activity

  1. github-actions
    added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    connectivityIssues involving networking or endpoint connectivity problems (disconnections)
    on May 26, 2026

  2. github-actions commented on May 26, 2026

    @github-actions
    github-actionsBot
    on May 26, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  3. MisterRound commented on May 26, 2026

    @MisterRound
    MisterRound
    on May 26, 2026

    This exact error is now tied into the broader stream/retry/state synthesis in #24260:

    #24260 (comment)

    The short source-level mapping is:

    • current codex-rs/codex-api/src/endpoint/responses_websocket.rs emits websocket closed by server before response.completed when a Responses WebSocket close frame arrives before a response.completed event;
    • current default retry budget is 5 stream retries, and release builds hide the first WebSocket retry notification, which explains why users often first see Reconnecting... 2/5;
    • after the retry budget, Codex attempts HTTP fallback for the session;
    • related reports show this exact path can combine with separate Desktop/session-state bugs such as unknown conversation, terminal turns restored as markedStreaming=true, and missing turn items.

    So I think this issue is a clean representative of the exact WebSocket-close subcluster, while #24260 is currently the broader cross-thread tracker for how this interacts with first-output stalls and Desktop state recovery.

  4. SkiesOfTheKuth commented on Sep 17, 2026

    @SkiesOfTheKuth
    SkiesOfTheKuth
    on Sep 17, 2026

    Bump wtf.

  5. PeytonWDYM commented on Sep 17, 2026

    @PeytonWDYM
    PeytonWDYM
    on Sep 17, 2026

    Bump

  6. leopingk commented on Sep 19, 2026

    @leopingk
    leopingk
    on Sep 19, 2026

    特么的这到底啥问题啊！

  7. sthilaire1 commented on Sep 25, 2026

    @sthilaire1
    sthilaire1
    on Sep 25, 2026

    bump

  8. XtremeSounds commented on Sep 25, 2026

    @XtremeSounds
    XtremeSounds
    on Sep 25, 2026

    happening to me right now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething 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