›_ Codex Issues
Codex Issues / #32728

Codex Desktop: new tasks fail with "no rollout found" while existing tasks continue

Open 💬 8 comments Opened Jul 13, 2026 by kevinyan815
💡 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 (From “About Codex” dialog)?

Codex Desktop 26.707.62119 (client version reported by the app-server log)

What subscription do you have?

Unknown (signed in with ChatGPT; plan name is not visible in the app)

What platform is your computer?

macOS Darwin 25.4.0 arm64

What issue are you seeing?

Creating any new task in Codex Desktop immediately shows:

Failed to resume task
no rollout found for thread id <new UUID>

Existing tasks can be opened and continued normally. The failure is limited to new task creation.

For a failing new task ID (019f5a28-43b8-78b2-b034-ea9e3f0b78a9), I verified locally that:

  • ~/.codex/state_5.sqlite has no row in threads for this ID.
  • No matching rollout JSONL exists under ~/.codex/sessions/.
  • The only associated local record is a temporary shell snapshot.

This indicates the app creates the thread ID but does not persist or materialize its rollout before attempting thread/resume.

What steps can reproduce the bug?

  1. Open Codex Desktop on macOS and sign in with ChatGPT.
  2. Open any existing task; it resumes and accepts follow-up messages.
  3. Click New task.
  4. Before entering any prompt, the app shows Failed to resume task with a newly generated thread ID.
  5. Repeat New task; each attempt has a different ID and the same error.

This still happens after updating the desktop app. I did not delete ~/.codex, because it contains working local task history.

What is the expected behavior?

New task should create and persist a new thread and rollout, then open an empty composer. Existing tasks should remain unaffected.

Additional information

  • Existing tasks continue normally; only fresh task creation fails.
  • CLI diagnostics report a consistent current installation, so the issue appears isolated to the Desktop new-thread path.
  • Related reports with similar missing-rollout behavior: #16872, #22001, and #14396. They do not appear to be exact duplicates.
  • I can provide redacted app-server log lines and the failing thread ID if needed. I have not attached full logs or local databases because they may contain private task content.

View original on GitHub ↗

8 Comments

github-actions[bot] contributor · 7 days ago

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

  • #32578

Powered by Codex Action

kevinyan815 · 7 days ago

The duplicate candidate #32578 was reported fixed in 26.707.61608. This issue reproduces on the later Codex Desktop client version 26.707.62119, and the error appears immediately after clicking New task. Therefore this appears to be a regression or a remaining variant rather than the already-fixed report.

Sowul · 7 days ago

It may have been fixed on Mac, but on Windows, new tasks (both in projects and projectless) haven't been working for about a month - still not fixed as of version 26.707.62119.

Sol-momma · 7 days ago

Environment

  • OS: macOS
  • Codex Desktop version: 26.707.62119
  • Existing tasks continued to work normally
  • Only new task creation failed

Error

When creating a new task, Codex displayed:

Failed to resume task
no rollout found for thread id <UUID>

Temporary workaround

I temporarily renamed my user-level Codex configuration file:

mv ~/.codex/config.toml ~/.codex/config.toml.disabled

After fully relaunching Codex Desktop, I was able to create new tasks again.

What this command does

  • It does not delete config.toml
  • It only renames the file
  • Codex can no longer load it under the expected filename
  • The original configuration remains available as config.toml.disabled

The configuration can be restored with:

mv ~/.codex/config.toml.disabled ~/.codex/config.toml

Configuration context

My config.toml contained:

  • Multiple MCP servers
  • Multiple plugins
  • Session-related hooks
  • Experimental or additional feature settings

Because the entire file was disabled, I have not yet identified the exact setting that triggers the issue.

Possible relation

This may be related to the MCP startup timeout reports in:

  • #29376
  • #29416

However, I cannot confirm that MCP is the root cause in my environment.

Current conclusion

  • Renaming config.toml restored new task creation in my environment
  • This is a temporary workaround
  • This is not a confirmed permanent fix
  • The exact root cause has not yet been isolated
AShortcuts · 4 days ago

I am experiencing the same issue on the current latest version. I can confirm the problem goes away and allows me to ask new questions and load chat history when I disable all mcps (aside from node_repl).

Sol-momma · 4 days ago

@AShortcuts Me either🤝

gustkiller · 4 days ago

same issue here with windows desktop app

gustkiller · 4 days ago

no rollout found for thread id 019f6ae0-b32f-74f3-9bcd-e584e884