Codex Desktop cannot create active thread on Windows #30748

Activity

1. joseferocheita-dotcom

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Jun 30, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Jun 30, 2026
3. github-actions commented on Jun 30, 2026

   

   github-actionsBot

   on Jun 30, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Unable to send message #29632
   • Unable to send messages in Codex App, stuck on "Could not send message" / "Loading..." #29311
   • Unable to create new threads, start conversations, or submit and push changes. #29421

   Powered by Codex Action
4. fibo-blip commented on Jul 1, 2026

   

   fibo-blip

   on Jul 1, 2026

   More actions

   This may be related to an older but still-open Windows session-state issue: #14251.

   I hit a current Windows Desktop case with the same user-visible family of symptoms (Unable to send message / Loading...), but local diagnostics pointed away from auth/network/plugin failure:

   • WSL mode runtime was healthy
   • codex doctor reported auth/network/websocket OK
   • disabling recently added plugins did not fix it
   • stale remote-control selection was not active in the failing run (hostId=local, remote connection count 0)

   The decisive log pattern was:

   maybe_resume_success
   latestTurnStatus=interrupted
   markedStreaming=true
   

   The affected local session JSONL had an interrupted turn ending with turn_aborted but no terminal assistant message / task_complete. Backing up the session file and appending a terminal assistant message plus task_complete for that interrupted turn_id made the Desktop composer usable again.

   I posted the fuller sanitized details here: #14251 (comment)

   So at least one current Windows Unable to send message / Loading... case is caused by stale streaming state after an interrupted turn, not by connectivity or WSL runtime failure.