3 people reported
All time, since Sep 14.
Completed turns return empty items
“Codex Desktop task-history reads can expose a completed/status record while omitting the retrievable message body.”
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/13993/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
Completed turns return empty items in task history reads. On macOS Desktop, a turn reads as completed with an empty items array although persisted history or rollout records contain the messages.
Is this your bug?
File my report- Where
- Desktop task history
- Versions
- 26.908.40834
- Platforms
- macOS
- How bad
- Breaks a normal workflow.
Part of: Thread history missing or unopenable12 bugs
- Threads fail to open3 people
- Response vanishes after streaming3 people
- Older turns missing from history3 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?
- Turns end before work finishes19 people
Original reports3, newest first
- Legacy completed turn has no projected items although its original rollout records surviveOn GitHub#50861
- [macOS][Desktop] Completed-turn history can return empty items instead of an explicit incomplete stateOn GitHub#47093
- macOS Desktop: completed turn returns empty items although history DB contains the final answerOn GitHub#45562