You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex Desktop new conversations spend several minutes at Reconnecting 5/5 before starting normally #29169
Codex Desktop eventually starts each new conversation/task normally, but almost every new task first spends several minutes in a pre-start reconnect/timeout state.
This is not a permanent failure. After I submit a prompt, Codex often shows Reconnecting 5/5 and request timed out before any real task progress appears. After that delay, the task usually starts and runs normally.
Once the task begins, streaming/output speed looks generally normal. The bottleneck is the time between prompt submission and the first real task activity.
Environment
Product: Codex Desktop
Version: 26.616.32156
Release shown in About dialog: Released Jun 19, 2026
macOS: Tahoe 26.5.1
Hardware: MacBook Pro 16-inch, Apple M5 Max, 128 GB memory
Observed pattern
Affected new conversations/tasks show a status like Worked for 7m 15s or Worked for 11m 14s, while still displaying Reconnecting 5/5 and request timed out. Then the task content appears and the conversation proceeds normally.
Expected behavior
A new task should begin shortly after the prompt is submitted. If a retry or fallback is needed, it should recover quickly rather than spending several minutes before each task starts.
Actual behavior
New tasks can start successfully, but they frequently start only after a long reconnect/timeout delay. This wastes usable time because the same pre-start stall repeats at the beginning of many new tasks.
changed the title [-]Codex Desktop stalls on Reconnecting 5/5 / request timed out before tasks start[/-][+]Codex Desktop new conversations spend several minutes at Reconnecting 5/5 before starting normally[/+]on Jun 20, 2026
After Codex Desktop has been idle / not used for a few hours, reopening it and sending the first request consistently starts with Reconnecting ... /5 and then request timed out.
Once the reconnect eventually succeeds, subsequent requests generally work normally.
The same behavior returns again after another multi-hour idle period.
This makes it look like a stale/expired connection or session is not being refreshed proactively before the first request after a long idle period. Ideally Codex should refresh/re-establish the connection on resume/open, so the first user request does not have to pay the reconnect timeout/retry cycle.
Activity
github-actions commentedon Jun 20, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-]Codex Desktop stalls on Reconnecting 5/5 / request timed out before tasks start[/-][+]Codex Desktop new conversations spend several minutes at Reconnecting 5/5 before starting normally[/+]HS-DE commentedon Sep 23, 2026
Additional reproduction pattern:
Reconnecting ... /5and thenrequest timed out.This makes it look like a stale/expired connection or session is not being refreshed proactively before the first request after a long idle period. Ideally Codex should refresh/re-establish the connection on resume/open, so the first user request does not have to pay the reconnect timeout/retry cycle.