3 people reported
All time, since Oct 9.
Threads fail to open
“Codex could recompute the byte offset from the ordinal (or offer a repair) instead of hard-failing.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/9285/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Threads fail to open after base rollout file shrinks. Paginated history lineage error appears in the desktop app when an external tool rewrote the base rollout in place.
Is this your bug?
File my report- Where
- Desktop app
- Error text
invalid paginated history lineage for <id>: cutoff byte offset is past the source rollout- Versions
- 0.160.0
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Part of: Thread history missing or unopenable12 bugs
- Response vanishes after streaming3 people
- Older turns missing from history3 people
- Completed turns return empty items3 people
- Chat replies go blank after switching4 people
- Remote chat history missing2 people
- Final answers not displayed3 people
- read_thread returns only content-reference placeholders for ChatGPT assistant replies8 people
- Thread history rolls back2 people
- Task transcript goes blank2 people
- Chats fail to open2 people
Show all 11Show only the largest 10
- Thread history projection stalls2 people
Not quite your bug?
- Migration drops subagent history4 people
Original reports3, newest first
- Paginated history stays stale after external rollout rewrite; request supported per-thread reindex recoveryOn GitHub#53793
- Windows desktop: existing chats fail to open with cutoff byte offset past the source rolloutOn GitHub#52551
- Thread unopenable: "cutoff byte offset is past the source rollout" although end_ordinal_exclusive identifies the correct offsetOn GitHub#52412