Codex Desktop on Windows: auth loop followed by intermittent Timeout and "no rollout found for thread id"

Codex
, ,
1

I’m experiencing an intermittent Codex Desktop issue on Windows.

Environment:

  • Codex Desktop: 26.820.60940
  • Windows 11 Pro 25H2
  • OS build: 26200.9168
  • Signed in with a ChatGPT account, not an API key

Sequence of events:

  1. Codex Desktop was initially working normally.
  2. While using it, I was unexpectedly redirected to sign in again.
  3. I then experienced an authentication/sign-in loop.
  4. After that, Codex began intermittently failing to create or continue conversations.
  5. A Codex update was installed later, but the problem still continues.

Errors I receive:

Conversation creation failed – Timeout

and sometimes, after the first response succeeds:

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

The problem is intermittent. Sometimes Codex works for one or more turns, then suddenly fails again.

Troubleshooting already performed:

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

The issue still reproduces.

I also submitted an in-app feedback report.

Related GitHub issue:

There are also related authentication/session reports such as #40699, but my case additionally includes conversation timeout and missing rollout/thread state.

Has anyone else started seeing this after the recent Windows Codex Desktop updates?

2

Kudos for creating an Codex Issue and linking here.

Did you take a look at the Related topics section below this topic.

3

Yes, I checked the Related topics section and also looked through several similar reports.

The closest ones I found are:

  • “Codex crashing Windows desktop app with one account only”
  • “[Windows][Codex Desktop][Auth] Advanced Account Security causes successful login to fail with HTTP 401 / auth_token_missing”
  • “Codex Desktop for Windows: token_revoked on /wham/tasks/list after fresh profile and Google OAuth login”

They are very similar to the authentication part of my issue: successful sign-in followed by a 401/auth state loss and another login prompt.

My case seems slightly broader because, after the authentication loop started, I also began seeing intermittent conversation creation timeouts and:

no rollout found for thread id ...

I also confirmed that Codex CLI works normally on the same Windows machine with the same account, while Codex Desktop remains affected.

So I suspect these reports may belong to the same broader Desktop authentication/session-state regression, but I kept my GitHub issue separate because of the additional timeout / rollout failures.