Summary
On Codex Desktop for macOS, a scheduled task can complete and persist its final response in its existing task thread, while that response is absent from the thread’s chat UI. This makes a healthy scheduler appear to have failed.
This concerns delivery into an existing continuing chat. Creating a separate standalone task per run is not an acceptable workaround.
Environment
- ChatGPT powered by Codex & OWL on macOS
- App version:
26.825.51511(About shows an August 29, 2026 release) - Recurring weekday heartbeat targeting an existing Codex task thread
- America/New_York
Confirmed evidence
- The Mac was awake with Codex Desktop open; running the same task manually succeeded.
- A controlled scheduled validation ran in the original existing thread at 5:45:16 PM ET on September 1 and completed at 5:45:31 PM ET (15.6 seconds).
- That scheduled turn restored the normal weekday configuration and persisted a final heartbeat notification in the same original thread.
- Earlier affected scheduled runs also had persisted final results, despite reports being absent from the expected desktop chat view.
This rules out the Mac being off, a general scheduler failure, or a permanently invalid target thread as sufficient explanations.
Expected behavior
For a scheduled task targeting an existing Codex chat, its completed final response should be appended and reliably rendered in that same chat.
Actual behavior
The scheduler can complete and persist the final result, but the existing chat can appear to contain no new report. There is no trustworthy app-visible delivery signal.
Reconstruction hypothesis, not proven
During scheduled-task resume, local Codex logs included:
ignored world-state patch without a full snapshot
The open-source reconstruction code ignores a partial world-state patch without a full-snapshot baseline. This is consistent with a display/history reconstruction failure, but it is not established as the direct cause.
Source: codex/codex-rs/core/src/session/rollout_reconstruction.rs at main · openai/codex · GitHub
A related macOS report describes completed task turns missing from task history after reopening:
Requested investigation
Please investigate scheduled-turn delivery into existing threads, especially resume and snapshot reconstruction. A structural fix should ensure persistence and user-visible history remain atomic from the user’s perspective, or provide a clear in-app recovery indicator when rendering fails.