Skip to content

Codex Desktop regression after 26.803.61601 update: WebSocket Broken pipe leaves task stuck #37894

Open

Description

@omarpinarecords

Description

Immediately after Codex Desktop updated at approximately 6:38 PM ET on August 10, 2026, an existing task became stuck after a WebSocket disconnect.

The user-visible error was:

stream disconnected before completion: failed to send websocket request: IO error: Broken pipe (os error 32)
stream disconnected before completion

Environment

  • Codex Desktop / ChatGPT app: 26.803.61601 (build 6396)
  • Standalone Codex CLI installed locally: 0.147.0
  • macOS
  • Local project task
  • Large, image-heavy session history: approximately 255 MB

Observed behavior

  1. The app updated at approximately 6:38 PM ET.
  2. A turn in an existing task then disconnected with the Broken pipe (os error 32) error above.
  3. Retrying in the same task was accepted but produced no assistant, reasoning, tool, completion, or visible error event.
  4. One retry remained empty for about three minutes before interruption.
  5. A subsequent retry remained active with no output, leaving the task stuck.
  6. Restarting/retrying in the same task did not recover it.

Expected behavior

After a transient WebSocket disconnect, the turn should either reconnect and complete, or terminate with a visible recoverable error so the task can be retried normally.

Diagnostics

An in-app performance trace was uploaded for this occurrence. Its feedback ID can be provided privately to an OpenAI maintainer on request.

Related older report: #32555. This issue documents a new occurrence on the current build immediately after today's app update.

No raw logs, prompts, local paths, task/thread IDs, feedback IDs, screenshots, or image payloads are included.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    connectivityIssues involving networking or endpoint connectivity problems (disconnections)
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Aug 10, 2026
  2. github-actions commented on Aug 10, 2026

    @github-actions
    Contributor
  3. omarpinarecords commented on Aug 10, 2026

    @omarpinarecords
    Author

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

    Powered by Codex Action

    Dont you see the date of the issues you paste versus mine? all was working fine and started at 6:38 pm.

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)sessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions