Repository navigation
Dot cannot continue an existing local Codex chat on a connected Windows computer #52222
Description
Summary
My Dot, Lexi, cannot send a read-only instruction to an existing local Codex chat on my connected Windows computer.
OpenAI’s documentation describes support for continuing existing local Codex tasks:
https://learn.chatgpt.com/docs/dots/tasks-and-memory
Environment
Installed Windows package versions:
- OpenAI.Codex: 26.1002.7124.0
- OpenAI.ChatGPT-Desktop: 1.2026.190.0
The computer is connected to the Dot. A Custom Rule permits routine development instructions to existing local Codex project chats within authorized tasks.
Reproduction
- Connect the Windows computer to the Dot.
- Identify an existing local Codex chat. The local Codex assistant independently confirmed that the target exists and is idle.
- Ask the Dot to send a read-only receipt test to that chat, without editing files or changing project state.
- The Dot attempts mcp__codex_apps__cloud_threads_send_message.
Actual result
The operation fails before delivery:
CloudThreadNotFoundError: The cloud thread was not found.
No receipt response is obtained.
Inspection of the Dot’s available tool descriptions and schemas found:
- cloud_threads_send_message addresses an existing cloud task.
- cloud_threads_list_threads lists cloud task IDs.
- cloud_threads_attach adds accessible persisted tasks as native task cards; no local-chat connection parameter is documented.
- cloud_threads_create can start a new task on a connected desktop, but has no existing-chat or resume parameter.
- Local send_message_to_thread and read_thread tools are not exposed.
No replacement chat was created during this test.
Expected result
The Dot can continue the identified existing local Codex chat using a supported native operation, or clearly explain any account, version, or task-eligibility requirement.
Diagnostic feedback
Feedback submitted through the desktop app with diagnostic logs.
Feedback ID:
01a11764-84e5-7a00-ad5e-fb98f6a3d8c1
Please clarify the supported route for existing local Codex chats and whether this capability is unavailable in my current configuration.
Activity
github-actions commentedon Oct 8, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Kamber88 commentedon Oct 8, 2026
Additional diagnostic result from the actual Dot conversation:
The Dot performed a JavaScript runtime check, rather than only inspecting its tool catalog:
No functions were invoked, and no task messages, task creation, or settings changes occurred.
This checks the exact namespace associated with the reported native-route success in #49482. That route is unavailable in my Dot’s current runtime.
I reviewed the suggested related reports #51722 and #51880. They overlap with existing-task access failures, but a shared root cause has not been established. #50171 also reports the Windows CloudThreadNotFoundError symptom.
Please clarify how the documented existing-local-Codex continuation capability is exposed to the Dot, or consolidate this report into the appropriate tracking issue while retaining its diagnostic feedback reference.