Skip to content

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

Closed
Closed
Desktop App on Windows 26.623.101652: Unable to send message (Loading...), previous build failed with "no rollout found for thread id"#31004
Labels
appIssues related to the Codex desktop appbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

Description

@ThEWiZ76
ThEWiZ76
opened on Jul 3, 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

Image Image Image

Activity

  1. github-actions
    added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Jul 3, 2026

  2. github-actions commented on Jul 3, 2026

    @github-actions
    github-actionsBot
    on Jul 3, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  3. fibo-blip commented on Jul 3, 2026

    @fibo-blip
    fibo-blip
    on Jul 3, 2026

    Adding another Windows Desktop data point that may help separate this from pure network/auth failures.

    Environment:

    • Windows 11
    • Codex Desktop MSIX package currently installed: OpenAI.Codex_26.623.13972.0_x64__2p2nqsd0c76g0
    • WSL mode enabled for agent/runtime
    • WSL runtime itself is healthy: integrated terminal reports Linux/WSL and $HOME=/home/yury
    • Current WSL Codex CLI override was verified and points to an existing binary: codex-cli 0.142.5
    • Windows user CODEX_HOME is unset
    • bundled dependencies runtime validates successfully via setup.ps1

    User-visible symptom:

    • After a Codex Desktop app restart, an existing chat can open but sending a simple message in that chat shows the modal:
    Unable to send message
Loading...

    New observation / workaround:

    • If I switch to a different chat after the app restart and send a simple test message there first, that message sends successfully.
    • After that, returning to the originally failing chat makes sending work there too.
    • This has reproduced more than once.

    So in this case the failure does not look like a permanently broken CLI/runtime/WSL setup. It looks like some Desktop-side conversation/session/composer initialization state is not ready for the first target chat after restart, while sending in another chat initializes enough shared state for the original chat to recover.

    This is different from the stale CODEX_CLI_PATH protocol-mismatch case in #29159: the CLI path is current and the WSL runtime is healthy. It also seems related to the broader Unable to send message / Loading... cluster in #29632, especially the reports where the first send attempt initializes enough state for later sends to work.

  4. ideajoker commented on Jul 8, 2026

    @ideajoker
    ideajoker
    on Jul 8, 2026

    The same

    Windows Codex Desktop
    App package: OpenAI.Codex_26.623.19656.0
    CLI/runtime: 0.142.5
    Project path: C:\dev\codex-empty
    Symptom: creating a new project conversation spins forever.
    Observation: backend/local rollout threads are created and recorded in .codex-global-state.json, but the project sidebar does not attach/open them.
    Example hidden thread ids:
    019f425c-554f-77e0-a395-cc4cfc3a0a97
    019f425e-68ff-77e0-9ce9-e495e34a18ab
    019f4261-60bc-7c31-959c-7732788d42d1
    Other project C:\dev\codex-test works normally.

  5. ThEWiZ76 commented on Jul 9, 2026

    @ThEWiZ76
    ThEWiZ76
    on Jul 9, 2026
    Author

    My issue was fixed with version 26.623.141536, closing issue

  6. ThEWiZ76
    closed this as completedon Jul 9, 2026
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 workingsessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions