36 people reported

All time, since Sep 14, including 8 thumbs-up on GitHub.

Thread history missing or unopenable

“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/themes/193/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

Fading. No reports and thumbs-up in the last 7 days and 1 the week before, down from 9 a week at the mid-October peak.

12 bugs in this theme

  1. read_thread returns only content-reference placeholders for ChatGPT assistant repliesNo workaround yet8 people
  2. Chat replies go blank after switchingHas a workaround4 people
  3. Threads fail to openHas a workaround3 people
  4. Response vanishes after streamingNo workaround yet3 people
  5. Older turns missing from historyNo workaround yet3 people
  6. Completed turns return empty itemsNo workaround yet3 people
  7. Final answers not displayedNo workaround yet3 people
  8. Remote chat history missingNo workaround yet2 people
  9. Thread history rolls backNo workaround yet2 people
  10. Task transcript goes blankHas a workaround2 people
Show all 12Show only the largest 10
  1. Chats fail to openNo workaround yet2 people
  2. Thread history projection stallsNo workaround yet2 people

What's included

  • Existing thread cannot be opened: "invalid paginated history lineage: cutoff byte offset is past the source rollout", seen after an external tool shrank the rollout file
  • History projection stops at a duplicated rollout ordinal ("expected ordinal N, got N-1"), so the thread shows an old state while new turns keep completing
  • Older completed turns are skipped in the conversation view or search results after pagination, though they remain in the saved transcript
  • Completed turn is returned with empty items or no latest assistant message, even though the history database holds the final answer
  • Desktop app, remote mobile view and app-server read APIs (thread/items/list, read_thread) all show the same gaps
  • Answer body turns blank or shows "Unable to load this reply" after switching conversations and returning

Not included

  • Conversations lost because the rollout files themselves were deleted or corrupted
  • Chats missing from the sidebar or thread list, as opposed to missing turns inside a chat
  • Slow loading of long conversations without missing content

Original reports28, newest first

  1. [macOS App] Native ChatGPT reference returns unreadable replies; agent diverts to browser loginOn GitHub#57155
  2. Windows: completed final answer is saved but invisible; New Window does not restore itOn GitHub#54299
  3. Conversation history skips completed turns after app updateOn GitHub#54051
  4. Paginated history stays stale after external rollout rewrite; request supported per-thread reindex recoveryOn GitHub#53793
  5. Desktop remote conversation shows only Worked for durations while persisted final responses display on mobileOn GitHub#53592
  6. Codex desktop chat history is not rendered after reopening a long chat in a remote SSH workspaceOn GitHub#53080
  7. [macOS Desktop][Chat] Completed long assistant answer missing from transcript while fully visible on webOn GitHub#52701
  8. Windows desktop: existing chats fail to open with cutoff byte offset past the source rolloutOn GitHub#52551
  9. [Windows Chat 26.1002.52244] Completed answer bodies disappear on chat revisit; duration and actions remainOn GitHub#52493
  10. [Mac][26.924.22138] Entire paragraphs disappear after streaming completesOn GitHub#52436
Show all 28Show only the newest 10
  1. Thread unopenable: "cutoff byte offset is past the source rollout" although end_ordinal_exclusive identifies the correct offsetOn GitHub#52412
  2. GPT-6 final response disappears immediately after streaming completes in Codex macOS Chat modeOn GitHub#52385
  3. Unable to load replyOn GitHub#52134
  4. Legacy completed turn has no projected items although its original rollout records surviveOn GitHub#50861
  5. Codex desktop: command-menu search does not locate old matches, and read_thread pagination can skip stored itemsOn GitHub#50479
  6. [Windows App] read_thread returns only chatgpt-content-reference for completed ChatGPT repliesOn GitHub#50329
  7. Remote Codex tasks show only the first user message and assistant reply after reopening.On GitHub#48610
  8. [macOS][Desktop] Completed-turn history can return empty items instead of an explicit incomplete stateOn GitHub#47093
  9. [macOS Desktop 26.915.31945] Older turns stay hidden despite complete paginated history projectionOn GitHub#46954
  10. Codex Desktop omits newer saved history segments and resumes from an obsolete checkpointOn GitHub#46873
  11. [macOS desktop] Transcript becomes entirely blank during active task; harness restart restores historyOn GitHub#46865
  12. Codex Desktop main task timeline stays blank while a long-running Goal remains activeOn GitHub#46424
  13. "Error creating chat / Failed to resume chat" after latest macOS updateOn GitHub#46341
  14. app-server: thread history projection stalls forever after a duplicated rollout ordinal ("expected N, got N-1"); thread/items/list and thread/turns/list stop reflecting new turnsOn GitHub#46316
  15. [Windows Desktop] Active thread rolls back to stale checkpoint after restart; same-day turns and project rename disappearOn GitHub#45877
  16. macOS desktop app cannot resume historical threads: initialTurnsPage rejected for paginated threadsOn GitHub#45673
  17. macOS Desktop: completed turn returns empty items although history DB contains the final answerOn GitHub#45562
  18. [Windows Codex App] Task repeatedly returns to stale history: duplicate ordinal blocks projectionOn GitHub#45473

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.