7 people reported
All time, since Sep 30, including 4 thumbs-up on GitHub.
Dot can't reach local threads
“The delegated desktop-executor tool catalog also lacks these native methods.”
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/14570/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 or message existing local Codex threads. Dot's tool catalog lacks list_threads, read_thread and send_message_to_thread; cloud_threads lookup of the local thread returns "thread not found".
Is this your bug?
File my report- Where
- Dot tool catalog
- Error text
thread not found- Versions
- 26.928.2636.0
- Platforms
- Windows
- 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
- Existing thread read fails5 people
- Dot local task creation fails3 people
- Thread tools missing from tasks5 people
- Remote session read fails5 people
- Dots tasks missing browser tools5 people
Show all 11Show only the largest 10
- Dot tasks missing browser tools10 people
Original reports3, newest first
- dot: native tools for existing local Codex threads are unavailableOn GitHub#49925
- Windows: dot lacks native tools to read or message an existing local Codex conversationOn GitHub#49862
- Desktop / Dot: native thread communication is asymmetric between local and cloud-backed conversationsOn GitHub#49788