RAP Sheet home
Install the bug reporting skill
Rank, 14 days: 25 on the Codex sheet
133 people reported

All time, since Sep 17, including 73 thumbs-up on GitHub.

Dot can't access 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/themes/182/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. 5 reports and thumbs-up in each of the last two weeks, down from 57 a week at the early-October peak.

12 bugs in this theme

  1. Dot cannot read local threadsNo workaround yet57 people
  2. Dot cloud task create and continue fail with UNKNOWNHas a workaround18 people
  3. Dot task coordination failsHas a workaround15 people
  4. Dot tasks missing browser tools10 people
  5. Dot can't reach local threadsNo workaround yet7 people
  6. list_threads/read_thread failNo workaround yet6 people
  7. Existing thread read failsNo workaround yet5 people
  8. Thread tools missing from tasksNo workaround yet5 people
  9. Remote session read fails5 people
  10. Dots tasks missing browser tools5 people
Show all 12Show only the largest 10
  1. codex_app MCP fails in dot tasksHas a workaround3 people
  2. Dot local task creation failsNo workaround yet3 people

What's included

  • cloud_threads.read rejects a local thread ID with 'unsupported placement format version' or 'unsupported placement region'
  • Native list_threads / read_thread calls fail with 'MCP error -32000: Codex app tool request failed'
  • Native codex_app list/read/send tools are missing from the dot's or delegated task's tool catalog
  • On Windows, codex_app MCP startup fails before initialize in dot-created tasks; reports tie it to a missing SystemRoot in the launcher environment
  • Dot sends to a local thread return NOT_FOUND while the local side can still message the dot
  • cloud_threads.send_message, list_environments and get_orbit_profile fail with 'The invoking thread is not attached to an active Aeon'

Not included

  • User-configured stdio MCP servers missing from Desktop tasks while the CLI works
  • Dot failing to create or message its own tasks
  • Follow-up messages rejected when the user replies in a dot-created or cloud task

Original reports61, newest first

  1. Unable to read existing local Codex conversations by ID on two authorized MacsOn GitHub#59552
  2. macOS: dot cannot read existing local Codex threads (DesktopThreadReadUnavailableError), while new delegated tasks workOn GitHub#58862
  3. macOS: dot native thread read returns DesktopThreadReadUnavailableError with connected, authorized desktopOn GitHub#58447
  4. [macOS][dots] Reading an existing local Codex thread fails with “unsupported placement format version 3”On GitHub#55551
  5. Windows existing-task routing failures: placement versions 2/3, NOT_FOUND, and recovery findingsOn the forum#1407857
  6. Windows existing-task routing failures leave dot unable to monitor local work: findings and recovery poolOn GitHub#55352
  7. dot cloud task continuation returns UNKNOWN; original admission outcome remains unqueryableOn GitHub#55326
  8. [dot / Windows] Existing local Codex chat read fails with unsupported placement format version 1 despite computer shown as allowedOn GitHub#54948
  9. Intermittent AppServerBackendRequestError / UNKNOWN when sending follow-ups to cloud tasksOn the forum#1406653
  10. Multiple dots fail to create or continue Codex Cloud tasks with UNKNOWN; direct UI worksOn the forum#1406644
Show all 61Show only the newest 10
  1. Windows: dot cannot directly read/message local project threads, and creation loses the supplied project associationOn GitHub#53619
  2. Codex App: cloud thread read fails with unsupported placement format version 2On GitHub#53553
  3. [ChatGPT Work Cloud] list_threads is exposed with local execution but failsOn GitHub#53177
  4. Authorized Windows dot cannot discover or read an existing local Codex thread; placement region 12 and CloudThreadNotFoundErrorOn GitHub#53124
  5. [macOS/dots] Native local thread list/read tools missing in existing reader task on app 26.1007.21159On GitHub#52906
  6. ChatGPT for Windows: dot read/send to selected local thread still fail after update (UNKNOWN / NOT_FOUND)On GitHub#52892
  7. dot cannot read user-created Codex threads: “unsupported placement format version” / “unsupported placement region”On GitHub#52873
  8. Dot cloud task creation fails with UNKNOWN while direct Codex web succeeds in the same saved environmentOn GitHub#52449
  9. Dot cloud task control regression: readable tasks return UNKNOWN/NOT_FOUND on continuation; direct resume also failsOn GitHub#52374
  10. dot cannot read Codex threads: unsupported placement regions 6 and 14On GitHub#52331
  11. [macOS / dots] Cannot read manually created Codex threads (placement format v2/v3); repeated app approvalsOn GitHub#52247
  12. 01a11417-fef1-746b-b86d-806c6a79a0cf - Delegated Codex Cloud task creation fails with UNKNOWN while direct UI creation succeedsOn GitHub#52135
  13. [Windows 26.930.7945.0][Work] Local executor online, but list_threads/read_thread fail with MCP -32000On GitHub#52063
  14. dot task failed to startOn GitHub#51985
  15. [macOS 26.1002.52244] Dot still cannot read the original Local Codex task: unsupported placement format version 2On GitHub#51880
  16. Dot cannot resolve active context: “The invoking thread is not attached to an active Aeon”On GitHub#51769
  17. Windows desktop 26.1002.52244: previously working dot task connection fails with “The invoking thread is not attached to an active Aeon”On GitHub#51757
  18. dot: environment discovery, task creation and child listing fail with active-Aeon errorOn GitHub#51746
  19. Dot task coordination fails: “The invoking thread is not attached to an active Aeon”On GitHub#51743
  20. Original active dot rejects environment discovery and task messaging: invoking thread is not attached to an active AeonOn GitHub#51742
  21. dot cannot create local tasks, reporting “not attached to an active Aeon”On GitHub#51730
  22. Dots existing Local-task access: placement-format errors versus documented continuation and recoveryOn GitHub#51722
  23. dot cloud task creation and continuation fail with AppServerBackendRequestError / UNKNOWN while manual creation worksOn GitHub#51372
  24. Windows: durable codex_app MCP startup fails while local thread tools work (26.930.31730)On GitHub#51000
  25. Windows: codex_app tools unavailable in dot-created tasks; recover after SystemRoot launcher workaroundOn GitHub#50982
  26. Windows dot orchestration: relayed authorization rejected and directly authorized local task cannot be read or messagedOn GitHub#50873
  27. 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
  28. Windows dot rejects existing local chat IDs (region 12 / formats 1 and 3); same-ID native read succeedsOn GitHub#50704
  29. Dot cannot read an existing local Work thread: unsupported placement format version 2On GitHub#50698
  30. [macOS][dot] Local task dispatch works, but native thread listing fails with MCP -32000On GitHub#50551
  31. Windows: dot cannot continue local Codex sessions; delegated sessions lack computer-use toolsOn GitHub#50511
  32. Dot cannot resume existing Windows Codex tasks: placement formats 3 and 2; local controls work in desktopOn GitHub#50440
  33. dot cannot continue an existing connected Windows local task: placement format version 2 and CloudThreadNotFoundErrorOn GitHub#50171
  34. Dot cloud_threads: create returns UNKNOWN and send_message returns CloudThreadNotFoundError for readable Codex Cloud taskOn GitHub#50168
  35. Dot cannot read existing remote Codex sessions: unsupported placement format versions 1 and 2On GitHub#50157
  36. macOS dot: local thread read rejects placement format v1 and delegated task loses native thread toolsOn GitHub#50077
  37. Dot cannot resume or create cloud tasks, while direct messages in the original tasks execute successfullyOn GitHub#50015
  38. dot cannot remotely read local Codex sessions; both existing and new sessions produce placement errorsOn GitHub#49997
  39. macOS: dot local task creation fails with DesktopTaskWorkspaceUnavailableError after update to 26.928.31416On GitHub#49952
  40. dot: native tools for existing local Codex threads are unavailableOn GitHub#49925
  41. Windows: dot lacks native tools to read or message an existing local Codex conversationOn GitHub#49862
  42. Remote MCP on Windows drops SystemRoot with Unix controller defaults; bundled Node aborts before initializeOn GitHub#49820
  43. Desktop / Dot: native thread communication is asymmetric between local and cloud-backed conversationsOn GitHub#49788
  44. Dots’ newly created tasks can be read, but dots cannot read codex’s existing dialogues.On GitHub#49766
  45. Windows Dots: reading an existing local Codex chat fails with unsupported placement region 8On GitHub#49746
  46. Dot cannot create or follow up with local Codex tasks in saved projectsOn GitHub#49729
  47. Windows MSIX: Dots connected-computer tasks lack browser and session tools; generated app-tools working directory points outside virtualised app dataOn GitHub#49562
  48. [Windows][dot/Work] Computer tasks lack browser/desktop tools: durable MCP startup failures and follow-up path errorOn GitHub#49488
  49. Windows desktop: dot fails to start local tasks with DesktopTaskWorkspaceUnavailableErrorOn GitHub#49423
  50. [Windows Desktop] fresh and resumed Tasks omit codex_app capability rootOn GitHub#46653
  51. [Windows Desktop] create_thread absent from tool manifest in a task that instructs agents to use itOn GitHub#46147

Do you work on Codex?

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

Claim a tool