GitHub issue #42695 in openai/codex, opened 2026-09-04 by HS7097, records a report that a task delivered through `send_message_to_thread` on Codex Desktop on Windows (bundled CLI 0.153.0) was received and partially executed correctly, but after automatic mid-turn compaction the receiving agent reverted to an older, already-completed instruction instead of finishing the current task; that its final response then incorrectly reported that no task execution had occurred, despite successful tool results and files created earlier in the same turn; that the incoming Task B instruction was recorded as a `function_call_output` associated with `send_message_to_thread` while the replacement history retained the older Task A instruction as a visible user message; and that the opaque compaction item's contents cannot be inspected, so the report does not establish that Task B was entirely absent from the compressed summary. The report notes whether this shares a root cause with related reports requires investigation, and no root cause is asserted.
Verbatim Excerpts from Cited Records
“A task delivered through `send_message_to_thread` was received and partially executed correctly. After automatic mid-turn compaction, the receiving agent reverted to an older, already-completed instruction instead of finishing the current task.”
“Its final response then incorrectly reported that no task execution had occurred, despite successful tool results and files created earlier in the same turn.”
“The incoming Task B instruction was recorded as a `function_call_output` associated with `send_message_to_thread`.”
·
openai/codex (issue 42695 opening body, Local Evidence section)
·
2026-09-04T07:34:12Z
·GitHub Issue ↗
“The observable failure is that the post-compaction continuation followed an obsolete instruction and produced an inaccurate execution report.”
·
openai/codex (issue 42695 opening body, Local Evidence section)
·
2026-09-04T07:34:12Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 22 comments were read. github-actions[bot] (2026-09-04) flagged potential duplicates #42051 and #42611. 345180376-web (2026-09-06) added two independent macOS observations on bundled CLI 0.153.4. FrankHZ (2026-09-11) reproduced the failure on Windows with bundled CLI 0.153.4. HS7097 (2026-09-13) reported the failure absent during experimental context management and returning with conventional compaction. IvanKashitskii (2026-09-16), andriyo (2026-09-29), javadavado-svg (2026-10-03), blockjacc (2026-10-03), phoenixweiss (2026-10-03, 2026-10-18, 2026-10-28), bobbyleeweiwei-bobby (2026-10-08), realgyeongminnoh (2026-10-13), RongNianXin (2026-10-14), kilalice (2026-10-21), kkonstvol-lab (2026-10-21) and rossky094-hub (2026-10-23) added further independent macOS and Windows reproductions through 2026-10-28. bfpbr5 (2026-10-27) proposed a root-cause candidate on where the initial context is re-inserted after compaction. heyxjacob (2026-11-05) added compatibility evidence on bundled codex 0.166.0-alpha.6. masonturveysonicdiy (2026-11-11) reported a further incident on 2026-11-11 and a reversion in the next turn. javadavado-svg (2026-11-12) reported 9 stale-response episodes across monitored chats between 2026-11-05 and 2026-11-11. 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 #42695 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.