macOS desktop app cannot resume historical threads: initialTurnsPage rejected for paginated threads
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Summary
All historical Codex desktop tasks fail to open. New tasks can be created, but existing tasks cannot be resumed.
Environment
- macOS
- ChatGPT/Codex desktop app version: 26.715.72359
- Bundled Codex CLI: 0.145.0-alpha.30
Steps to reproduce
- Open the Codex desktop app.
- Select any historical task.
- The task fails immediately instead of opening.
Actual result
The app shows:
paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor
Identifiers
- Session ID: no-active-thread-01a0a4a6-b341-71d3-a764-30f4a0464b0b
- Failing conversation ID: 019f8916-3cd6-70a0-ba67-3f80e771cfb7
- Failing conversation ID: 01a09155-c622-7f22-b430-128649ec1d13
Expected result
The selected historical task should open and resume normally.
Additional information
New Codex chats open normally; only historical task resume fails.
First observed: September 15, 2026 (Europe/Berlin).
Relevant log output:
Request failed ... error={"code":-32600,"message":"paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor"} method=thread/resume
Failed to resume conversation ... errorMessage="paginated threads do not support initialTurnsPage; use turnsBackwardsCursor and itemsBackwardsCursor"
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
Start by tracing the macOS desktop app's thread/resume request into the bundled Codex CLI, focusing on the initialTurnsPage rejection. Compare the paginated-thread handling with the turnsBackwardsCursor and itemsBackwardsCursor fields named in the error. Done means historical tasks open and resume normally while new chats continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100