›_ Codex Issues
Codex Issues / #31004

Desktop App on Windows 26.623.101652: Unable to send message (Loading...), previous build failed with "no rollout found for thread id"

Resolved 💬 4 comments Opened Jul 3, 2026 by ThEWiZ76 Closed Jul 9, 2026

Summary

After updating to Desktop version 26.623.81905, the Codex Desktop App became unusable.

The issue started immediately after updating.

The web version of Codex and the Codex CLI continue to work normally, so this appears to be specific to the Desktop application.

The issue is isolated to the Desktop App:

  • ChatGPT Web works
  • Codex Web works
  • Codex CLI works
  • API connectivity has been verified (Test-NetConnection api.openai.com -Port 443 succeeds)

This appears to be Desktop-specific.

---

Environment

  • OS: Windows 11
  • Codex Desktop: 26.623.101652
  • Shell: PowerShell 7
  • Network: Direct connection (no VPN changes)
  • Account: ChatGPT Pro

---

Expected behavior

  • Create a new chat
  • Send messages in existing chats
  • Create and start tasks

---

Actual behavior

Initially (before update on version 26.623.81905)

Creating a new chat failed with:

Error starting chat
Timeout

Creating a task failed with:

Error creating task
Timeout

Later this changed into:

Error creating task
no rollout found for thread id <thread-id>

---

Current behavior

The application now allows opening existing conversations, but no messages can be sent.

Attempting to send any message displays:

Unable to send message
Loading...

The dialog never resolves and never displays a more detailed error.

---

What works

✅ ChatGPT Web
✅ Codex Web
✅ Codex CLI

---

What does not work

  • ❌ Creating new chats in the Desktop App
  • ❌ Creating tasks in the Desktop App
  • ❌ Sending messages in existing Desktop conversations

---

Troubleshooting performed

  • Restarted application
  • Restarted Windows
  • Verified network connectivity
  • Verified api.openai.com:443 is reachable
  • No VPN changes
  • No antivirus changes
  • No firewall changes

PowerShell:

Test-NetConnection api.openai.com -Port 443

TcpTestSucceeded : True

---

Additional observations

  • The Desktop application creates a thread ID successfully.
  • The backend then responds:
no rollout found for thread id ...

This suggests thread creation succeeds but the rollout/task initialization fails.
The issue appears isolated to the Desktop application because both the web interface and CLI continue functioning normally.

---

Regression / version history

This appears to be a continuing Desktop App regression across recent builds.

  • The version before 26.623.81905 worked correctly.
  • After updating to 26.623.81905, the Desktop App started failing when creating new chats/tasks.
  • After updating again to 26.623.101652, the behavior changed: existing conversations can open, but sending messages now fails with Unable to send message / Loading....

So this is not a regression introduced only in 26.623.101652. The issue started in 26.623.81905 and persists, with changed symptoms, in 26.623.101652.

Screenshots

<img width="362" height="234" alt="Image" src="https://github.com/user-attachments/assets/cbb2ba9e-97f4-4bf8-9404-990ba3626d82" />

<img width="925" height="251" alt="Image" src="https://github.com/user-attachments/assets/bb583f50-0b11-4b7a-98d7-a9603b11d02a" />

<img width="782" height="208" alt="Image" src="https://github.com/user-attachments/assets/30a532fc-5893-4863-98b0-676da6e99d7d" />

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗