`Codex: "failed to read thread" thread-store internal error (CRC / os error 23) prevents opening/resuming a session`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Codex app version: 26.908.70816 (personal workspace)
Error: In the original chat/thread, opening, resuming, and sending messages all fail with:
failed to read thread … CRC (os error 23)
Shared link: The shared link (https://chatgpt.com/s/...) is viewable (I can see the content), but it is not interactive / I can’t continue the conversation from that page.
Feedback ID: 01a0812f-8190-79a3-a532-b6b1d6bc6b55
No session ID shown: The feedback completion screen did not show an Uploaded thread… message or any separate session ID.
Backups created (original not modified): I backed up the following paths:
~/.codex/sessions
~/.codex/archived_sessions
(macOS) ~/Library/Logs/com.openai.codex/...
CRC errors reproduce in some session files as well. (Original files were not modified.)
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 reviewing the backed-up files under ~/.codex/sessions and ~/.codex/archived_sessions, then inspect the macOS logs under ~/Library/Logs/com.openai.codex/.... Reproduce opening, resuming, or sending a message in the affected thread and compare the CRC/os error 23 with the session files. Done means the affected session can be opened and resumed without the thread-store error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100