GitHub issue #58447 in openai/codex, opened 2026-10-30 by Robert-Fish, records a report that a dot cannot read an existing user-created native Codex thread on a connected macOS desktop through the documented cloud_threads.read route, despite the desktop reporting connected, attached, and authorized for tasks; that a control read of an existing dot-created cloud task succeeds; and that the read fails with DesktopThreadReadUnavailableError (CONFLICT / desktop_thread_read_unavailable), with no root cause asserted.
Verbatim Excerpts from Cited Records
“A dot cannot read an existing user-created native Codex thread on a connected macOS desktop through the documented `cloud_threads.read` route.”
“The selected desktop reports `status=connected`, `attached=true`, and `is_authorized_for_tasks=true`.”
·
openai/codex (issue 58447 opening body, Reproduction section)
·
2026-10-30T22:37:37Z
·GitHub Issue ↗
“A read of an existing dot-created cloud task, with its thread ID and no environment ID, returns `isError=false`.”
·
openai/codex (issue 58447 opening body, Successful control section)
·
2026-10-30T22:37:37Z
·GitHub Issue ↗
“The error does not establish whether this is a client-version/capability issue, an unmet setting, or another native-read failure. No root cause is asserted.”
·
openai/codex (issue 58447 opening body, Diagnostic limits section)
·
2026-10-30T22:37:37Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 23 comments were read. Robert-Fish (2026-10-30) adds a same-thread control: the supported local read_thread route with hostId="local" successfully read the same native thread. jimmytju-rgb (2026-10-31) independently reproduces on macOS with ChatGPT desktop 26.1027.30824 build 22943, and reports the failure persists after a user-performed Revoke/Allow reconnection. guansk (2026-10-31) adds another macOS case on build 22530. Multiple Windows reproductions follow (personaledward-hash 2026-11-01, zxshm 2026-11-03, powermac84 2026-11-03 on Mac Studio, Nelsitou 2026-11-04, and others through 2026-11-11), all with the same error and the local route working. rrabeloparreira (2026-11-06) reports support replied with an AI-signed explanation that connecting a computer does not guarantee access to every existing conversation. dram-solutions (2026-11-09 to 2026-11-11) reports Debian observations, including one local fault repaired while preserving both profiles. MSTmortoring (2026-11-06) reports a workaround using a fresh local task. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #58447 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.