RAP Sheet home
Install the bug reporting skill
Its theme's rank, 14 days: 25 on the Codex sheet
57 people reported

All time, since Sep 30, including 33 thumbs-up on GitHub.

Dot cannot read local threads

“Reading these threads fails with backend errors, even though my Windows desktop is connected and dot can discover my local Codex projects.”

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/9680/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

Still happening. 2 reports and thumbs-up in each of the last two weeks, down from 21 a week at the early-October peak.

Dot cannot read existing local Codex threads: unsupported placement. cloud_threads.read fails with "unsupported placement region" or "unsupported placement format version" while the computer is "connected, attached, and authorized".

Is this your bug?

File my report
Where
Dots thread access
Error text
AppServerBackendRequestError: Client specified an invalid argument: post-cutover thread ID [LOCAL_CHAT_ID] has unsupported placement region 8
Versions
0.160.0 to 26.1007.30912
Platforms
macOS, Windows
How bad
Breaks a normal workflow.

Part of: Dot can't access local threads12 bugs

  1. Dot cloud task create and continue fail with UNKNOWN18 people
  2. Dot task coordination fails15 people
  3. list_threads/read_thread fail6 people
  4. codex_app MCP fails in dot tasks3 people
  5. Dot can't reach local threads7 people
  6. Existing thread read fails5 people
  7. Dot local task creation fails3 people
  8. Thread tools missing from tasks5 people
  9. Remote session read fails5 people
  10. Dots tasks missing browser tools5 people
Show all 11Show only the largest 10
  1. Dot tasks missing browser tools10 people

Original reports25, newest first

  1. [macOS][dots] Reading an existing local Codex thread fails with “unsupported placement format version 3”On GitHub#55551
  2. Windows existing-task routing failures: placement versions 2/3, NOT_FOUND, and recovery findingsOn the forum#1407857
  3. Windows existing-task routing failures leave dot unable to monitor local work: findings and recovery poolOn GitHub#55352
  4. [dot / Windows] Existing local Codex chat read fails with unsupported placement format version 1 despite computer shown as allowedOn GitHub#54948
  5. Windows: dot cannot directly read/message local project threads, and creation loses the supplied project associationOn GitHub#53619
  6. Codex App: cloud thread read fails with unsupported placement format version 2On GitHub#53553
  7. Authorized Windows dot cannot discover or read an existing local Codex thread; placement region 12 and CloudThreadNotFoundErrorOn GitHub#53124
  8. ChatGPT for Windows: dot read/send to selected local thread still fail after update (UNKNOWN / NOT_FOUND)On GitHub#52892
  9. dot cannot read user-created Codex threads: “unsupported placement format version” / “unsupported placement region”On GitHub#52873
  10. dot cannot read Codex threads: unsupported placement regions 6 and 14On GitHub#52331
Show all 25Show only the newest 10
  1. [macOS / dots] Cannot read manually created Codex threads (placement format v2/v3); repeated app approvalsOn GitHub#52247
  2. [macOS 26.1002.52244] Dot still cannot read the original Local Codex task: unsupported placement format version 2On GitHub#51880
  3. Dots existing Local-task access: placement-format errors versus documented continuation and recoveryOn GitHub#51722
  4. Windows dot orchestration: relayed authorization rejected and directly authorized local task cannot be read or messagedOn GitHub#50873
  5. Codex Cloud threads API: reading a local Codex thread fails with "unsupported placement format version 2"; cloud_threads_create returns invalid argument on a connected & authorized environmentOn GitHub#50780
  6. Windows dot rejects existing local chat IDs (region 12 / formats 1 and 3); same-ID native read succeedsOn GitHub#50704
  7. Dot cannot read an existing local Work thread: unsupported placement format version 2On GitHub#50698
  8. Windows: dot cannot continue local Codex sessions; delegated sessions lack computer-use toolsOn GitHub#50511
  9. Dot cannot resume existing Windows Codex tasks: placement formats 3 and 2; local controls work in desktopOn GitHub#50440
  10. dot cannot continue an existing connected Windows local task: placement format version 2 and CloudThreadNotFoundErrorOn GitHub#50171
  11. macOS dot: local thread read rejects placement format v1 and delegated task loses native thread toolsOn GitHub#50077
  12. dot cannot remotely read local Codex sessions; both existing and new sessions produce placement errorsOn GitHub#49997
  13. Dots’ newly created tasks can be read, but dots cannot read codex’s existing dialogues.On GitHub#49766
  14. Windows Dots: reading an existing local Codex chat fails with unsupported placement region 8On GitHub#49746
  15. Dot cannot create or follow up with local Codex tasks in saved projectsOn GitHub#49729

Do you work on Codex?

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

Claim a tool