Its theme's rank, 14 days: 25 on the Codex sheet
5 people reported
All time, since Oct 1, including 4 thumbs-up on GitHub.
Remote session read fails
“Reads of two explicitly supplied session IDs failed with the same error family, with placement format versions 2 and 1 respectively.”
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/14440/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
Dot cannot read existing remote sessions: unsupported placement format version. Reads of explicitly supplied remote session IDs return no contents, with an invalid argument error naming placement format version 1 or 2.
Is this your bug?
File my report- Where
- Dot session reads
- Error text
AppServerBackendRequestError: Client specified an invalid argument: post-cutover thread ID [redacted] has unsupported placement format version 2- Versions
- 0.160.0
- Platforms
- iOS
- How bad
- Breaks a normal workflow.
Part of: Dot can't access local threads12 bugs
- Dot cannot read local threads57 people
- Dot cloud task create and continue fail with UNKNOWN18 people
- Dot task coordination fails15 people
- list_threads/read_thread fail6 people
- codex_app MCP fails in dot tasks3 people
- Dot can't reach local threads7 people
- Existing thread read fails5 people
- Dot local task creation fails3 people
- Thread tools missing from tasks5 people
- Dots tasks missing browser tools5 people
Show all 11Show only the largest 10
- Dot tasks missing browser tools10 people
Original reports1, newest first
- Dot cannot read existing remote Codex sessions: unsupported placement format versions 1 and 2On GitHub#50157