openai / openai/codex

[Bug] Codex Desktop conversations repeatedly hang in reconnect state on Windows

Open
#43,810 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug connectivity windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

Today (2026-09-08, Asia/Japan), I encountered this problem multiple times in Codex Desktop: conversations became stuck in the reconnect / reconnecting state and did not recover normally.

Environment

  • Product: Codex Desktop
  • OS: Windows (exact build not captured)
  • Codex version: unknown; the About dialog version was not captured
  • Date: 2026-09-08
  • Region/time zone: Asia/Japan

Actual behavior

Multiple conversations entered the reconnecting state. In several cases the conversation remained stuck instead of cleanly resuming, making the task unusable without abandoning or restarting the conversation.

Expected behavior

After a temporary connection or stream interruption, Codex should either resume the conversation reliably or fail promptly with a clear error and a manual retry/resume action. It should not remain indefinitely in a reconnect loop/state.

Reproduction / frequency

The issue occurred multiple times today across conversations. I do not yet have a minimal deterministic reproduction; it appears intermittent.

Additional context

This appears related to existing reports about repeated reconnect loops and stream disconnects, but this report is from a Windows desktop environment and records repeated occurrences on the same day.

I can provide logs and exact app/build details if maintainers indicate which files are needed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the report. First collect the Codex version, Windows build, and relevant logs, then investigate the reconnect behavior across the affected conversations. Done means temporary interruptions either resume reliably or produce a clear error with a manual retry or resume action.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.