Skip to content

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

Open
Open
Codex Desktop: new tasks fail with "no rollout found" while existing tasks continue#32728
Labels
appIssues related to the Codex desktop appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archiving

Description

@kevinyan815
kevinyan815
opened on Jul 13, 2026

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

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

Activity

  1. kevinyan815
    added
    appIssues related to the Codex desktop app
    on Jul 13, 2026
  2. github-actions
    added
    bugSomething isn't working
    app-serverIssues involving app server protocol or interfaces
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Jul 13, 2026

  3. github-actions commented on Jul 13, 2026

    @github-actions
    github-actionsbot
    on Jul 13, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  4. kevinyan815 commented on Jul 13, 2026

    @kevinyan815
    kevinyan815
    on Jul 13, 2026
    Author

    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.

  5. Sowul commented on Jul 13, 2026

    @Sowul
    Sowul
    on Jul 13, 2026

    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.

  6. Sol-momma commented on Jul 13, 2026

    @Sol-momma
    Sol-momma
    on Jul 13, 2026

    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:

    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

  7. AShortcuts commented on Jul 16, 2026

    @AShortcuts
    AShortcuts
    on Jul 16, 2026

    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).

  8. Sol-momma commented on Jul 16, 2026

    @Sol-momma
    Sol-momma
    on Jul 16, 2026

    @AShortcuts Me either🤝

  9. gustkiller commented on Jul 16, 2026

    @gustkiller
    gustkiller
    on Jul 16, 2026

    same issue here with windows desktop app

  10. gustkiller commented on Jul 16, 2026

    @gustkiller
    gustkiller
    on Jul 16, 2026

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

  11. rayrayraykk commented on Jul 22, 2026

    @rayrayraykk
    rayrayraykk
    on Jul 22, 2026

    Disable openaiDeveloperDocs MCP could be fixed.

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 appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingsessionIssues involving session (thread) management, resuming, forking, naming, archiving

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions