›_ Codex Issues
Codex Issues / #40704

[Windows][Codex Desktop 26.820.60940] Auth loop followed by intermittent Timeout and "no rollout found for thread id"

Open 💬 3 comments Opened Aug 25, 2026 by chelebyy
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using?

26.820.60940

What subscription / sign-in method are you using?

Signed in with a ChatGPT account (not an API key).

What platform are you using?

  • Windows 11 Pro
  • Version: 25H2
  • OS build: 26200.9168
  • Windows Feature Experience Pack: 1000.26100.344.0

What issue are you seeing?

Codex Desktop became unstable after an authentication/sign-in problem and now intermittently fails to create or continue conversations.

The sequence was:

  1. Codex was working normally.
  2. While using the app, it unexpectedly redirected me to sign in again.
  3. I then experienced a sign-in/authentication loop.
  4. After that, Codex began intermittently failing when creating or continuing chats.
  5. A Codex Desktop update was installed afterwards, but the issue still reproduces on 26.820.60940.

The errors include:

Conversation creation failed – Timeout

and sometimes, after a first response succeeds:

Unable to continue conversation
no rollout found for thread id 01a03a94-1d57-76e2-9be7-87e0979fe125

The problem is intermittent rather than constant. Sometimes Codex works for one or more turns, then suddenly fails again with either a timeout or the missing-rollout error.

Troubleshooting already performed

I have already tried all of the following:

  • Disabled all MCP servers
  • Signed out and signed back in
  • Fully restarted Codex Desktop
  • Fully restarted Windows
  • Tried multiple new conversations
  • Tested on a completely different network using a mobile hotspot

The issue still reproduces, so it does not appear to be caused by MCP initialization or my primary network/router/ISP.

In-app feedback

I also attempted to submit an in-app bug report. The first upload attempt failed, but a later retry appeared to succeed.

Feedback ID from the failed upload attempt:

01a03a9d-1631-7993-bfd7-8c26cc95cd41

Expected behavior

After authentication succeeds, Codex Desktop should remain signed in and conversations should be created and continued reliably without intermittent timeouts or missing thread/rollout state.

Additional information

This may be related to the authentication/session-state issue reported in #40699, but my case appears to progress further: after the auth loop, conversation creation/continuation also becomes unstable and thread/rollout state can no longer be found.

Because the issue persists after updating the app, across multiple restarts, with all MCPs disabled, and on a different network, it appears likely to be a Codex Desktop session/thread/backend-state issue rather than a local MCP or routing issue.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 2 days ago

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

  • #40699
  • #39829
  • #40074

Powered by Codex Action

chelebyy · 1 day ago

Additional detail: I am using a FEITIAN ePass K9 Plus physical FIDO2 security key with Advanced Account Security.

This may be relevant because other recent Windows Codex Desktop reports also mention passkey / hardware security key authentication, including #40888 and #40761. In my case, authentication succeeds, but Codex later enters reauthentication/session/thread failures.

chelebyy · 1 day ago

Additional isolation result: the same ChatGPT account works normally in Codex CLI on the same Windows machine. I can authenticate and continue multi-turn sessions there without the Desktop timeout, auth-loop, or no rollout found for thread id errors.

This strongly suggests the issue is specific to Codex Desktop's authentication/session/thread state handling rather than the account itself or general Codex authentication.