Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C047 Supported 2026-11-07

GitHub issue #50168 in openai/codex, opened 2026-10-02 by IaHorrorLabs, records a report that Dot can list and read Codex Cloud tasks but the exposed cloud_threads write path fails for both task creation and follow-up messaging, that new cloud task creation returned an app-server backend failure with error_code UNKNOWN and no usable thread or turn identity, and that a follow-up message to a manually created healthy cloud thread returned CloudThreadNotFoundError with error_code NOT_FOUND, observed on October 1, 2026.

Verbatim Excerpts from Cited Records
“Dot can **list/read Codex Cloud tasks**, but the exposed `cloud_threads` write path fails for both task creation and follow-up messaging.”
— IaHorrorLabs · openai/codex (issue 50168 opening body, Summary section) · 2026-10-02T04:04:41Z ·GitHub Issue ↗
“This is a **cloud-to-cloud Dot → Codex Cloud interoperability failure**, not a local Desktop-thread case.”
— IaHorrorLabs · openai/codex (issue 50168 opening body, Summary section) · 2026-10-02T04:04:41Z ·GitHub Issue ↗
“Multiple bounded attempts to create a Codex Cloud task in an existing, known-working cloud environment returned an app-server/backend failure with `error_code: UNKNOWN` and no usable thread/turn identity.”
— IaHorrorLabs · openai/codex (issue 50168 opening body, Actual behavior section) · 2026-10-02T04:04:41Z ·GitHub Issue ↗
“A Codex Cloud task was created manually in the same working environment and completed normally.”
— IaHorrorLabs · openai/codex (issue 50168 opening body, Actual behavior section) · 2026-10-02T04:04:41Z ·GitHub Issue ↗
Counter-record: Issue remains open with 29 comments as of 2026-11-05; no maintainer resolution appears in the surveyed thread. Multiple independent reproductions from 2026-10-03 to 2026-10-23 (jgilfoil, grtninja, NaturalMatchaKing, dean1012, xrl, familycoyne, KalGuinn, rogerafreeman, RaymondYueng) confirm the readable-but-not-messageable pattern for user-created cloud tasks and the UNKNOWN creation failure. Partial recovery reports exist for a different sub-case: jgilfoil on 2026-10-04 found a fresh Dot-created task could be created and messaged, and joshyorko on 2026-10-11 showed the same split, with Dot-created tasks working while user-created tasks still failed to accept sends; shevvek-chatgpt on 2026-10-22 reported reads and continuation recovered after a separate authorization-error episode. The latest surveyed comment, iszhihaoding on 2026-11-05, reports a related project-scoped creation failure. Surveyed thread contains no maintainer fix or closure. The claim documents only the original report, not a verified current state. Falsification probe: If issue 50168 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.

See also: Codex vs Cursor head-to-head comparison on 9bests