[macOS] Recent turns disappear after restart although messages remain in local rollout JSONL

What version of the Codex App are you using (From “About Codex” dialog)?

Current installed/running desktop app: 26.903.71938 (build 8576), bundle identifier com.openai.codex. The installed application is currently named ChatGPT.app. These values were read from its bundle metadata; the exact version at the first occurrence was not separately captured.

What subscription do you have?

Not provided in this report.

What platform is your computer?

macOS 26.6.2, Apple Silicon.
uname -mprs: Darwin 25.6.0 arm64 arm

What issue are you seeing?

Recent completed turns disappear from an existing long-running local task's visible conversation history after restarting the desktop app. Read-only inspection confirms that multiple missing user messages and final assistant replies still exist in the task's original local rollout JSONL.

First noticed on September 9, 2026; still reproducible on the affected task on September 10 (Asia/Shanghai).

The UI's history stops at a completed turn from September 8. Newly exchanged messages may be visible while working, but after restart the history returns to the same old endpoint. The app's available read_thread tool also returns September 8 as the newest completed turn, even though the raw rollout contains later messages.

This is a mismatch between raw stored messages and the history returned/displayed, not evidence that all missing messages were physically deleted.

What steps can reproduce the bug?

There is no deterministic minimal reproduction on a new task yet. The observed sequence on the affected task is:

1. Continue working in an existing long-running local task across multiple days.
2. Complete additional user/assistant turns on September 9.
3. Notice that intermediate recent turns are absent from the visible history.
4. Restart the desktop app and reopen the same task.
5. Observe that even the recent discussion about the missing history no longer appears; history again ends at the September 8 checkpoint.
6. Read the task through read_thread: its newest-first results also stop at that checkpoint.
7. Inspect the original session JSONL read-only: September 9 user messages and final assistant replies are still present.

Sanitized examples of retained raw records:

• September 9, 05:57:23 UTC: user message.
• September 9, 06:12:53 UTC: final assistant reply.
• September 9, 06:45:52 UTC: user message.
• September 9, 06:47:21 UTC: final assistant reply.

No message text is included here.

In-app feedback/session ID supplied after reporting the problem:
019fb5de-a749-7dd1-a446-bf6c86928ed7
This is also the affected task ID; it is not claimed to be a separate support ticket number.

What is the expected behavior?

Reopening a task should display its retained completed turns. If history reconstruction fails, the app should show an actionable error rather than silently presenting stale history.

Please advise on a supported, non-destructive recovery or history-rebuild procedure that preserves the original transcript.

Additional information

• Restarting did not restore the missing history.
• Inspection was read-only; no session/database editing, cache reset, task deletion, or repair reinstall has been performed as part of this investigation.
• No raw transcript, project files, screenshots, account credentials, or application logs are attached publicly.
• The root cause has not been established; this report does not assert an ordinal mismatch, index corruption, or Remote Control involvement.
• Potentially related: #42197 and #43434 (Windows/remote-session stale-history reports). #44015 reports older history being unavailable, while this case loses newer turns and returns a stale endpoint. Please link/close as a duplicate if the maintainers confirm the same underlying issue.

Start with the affected task's original local rollout JSONL and the read_thread entry point, comparing retained September 9 records with the history endpoint returned after restart. Reproduce the stale September 8 endpoint if possible; done means retained completed turns are displayed after reopening, or an actionable error is shown instead of stale history.