Codex Desktop: Failed to resume chat paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Version 26.715.72359
What subscription do you have?
Corp
What platform is your computer?
macOS
What issue are you seeing?
When I try to open or resume any previous Codex thread, I receive this error:
Failed to resume chat
paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor
The issue affects all existing threads, not just one. The thread titles/previews are still visible, but their conversation contents cannot be loaded.
I have already restarted the app, updated it to the latest version, and signed out and back in. The problem persists.
What steps can reproduce the bug?
- Open the Codex desktop app.
- Go to the thread history/sidebar.
- Click any existing/previous thread.
- Wait for the thread to load.
Expected result: The selected thread opens and its conversation history is displayed.
Actual result: The thread fails to load and shows the error:
“Failed to resume chat — paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor”
What is the expected behavior?
Previously created Codex threads should open normally and display their full conversation history, including messages and tool outputs, without any error.
Additional information
The problem happens with every previous thread I try to open. Thread titles and previews are still visible in the sidebar, but the conversation content does not load.
I restarted the app, updated it, and signed out and back in, but the issue persists. This prevents me from accessing my conversation history.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the failure from the Codex Desktop thread history and tracing the resume flow where paginated threads reject initialTurnsPage; inspect how turnsBackwardsCursor and itemsBackwardsCursor are handled. Done means existing threads open and display their conversation history, including messages and tool outputs, without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100