[Windows Desktop] Active thread rolls back to stale checkpoint after restart; same-day turns and project rename disappear

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

Not captured before the affected restart

What subscription do you have?

Not provided

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

A long-running local Codex Desktop task displayed its full, current conversation immediately before a clean application shutdown. After reopening the application and opening the same task, the visible conversation rolled back to an older checkpoint. The intermediate same-day conversation, tool results, and a project rename no longer appeared.

This was not an archive or delete action. It is a data-loss-class UX failure: work was visible before restart, but afterward the user cannot verify or recover it through the normal UI.

Before restart: the current afternoon conversation and project rename were visible.
After restart: the task rendered an older transcript ending at approximately 09:00 local time; the intervening morning and afternoon turns were absent. The task itself still appeared, making the stale history look authoritative.

What steps can reproduce the bug?

1. Use a long-running local Codex Desktop task on Windows.
2. Confirm the current conversation is fully visible.
3. At approximately 13:16 Asia/Taipei on 2026-09-16, capture a screenshot showing the current thread and a project rename in the sidebar.
4. Fully close Codex Desktop.
5. Reopen Codex Desktop and open the same task.
6. Observe that the visible transcript has rolled back to an older checkpoint (approximately 09:00 local time); the intermediate same-day conversation and project rename are no longer visible.

No destructive repair was attempted: no cache clear, no .codex deletion, no reinstall, and no local state database modification.

What is the expected behavior?

A conversation visible immediately before a clean shutdown must reconstruct to the same durable state after restart. Local project metadata, including a project rename, must not revert or disappear. If reconstruction fails, the app should present a clear recovery error and a non-destructive recovery path rather than silently displaying a stale partial transcript.

Additional information

Impact: loss of working context and inability to verify decisions or completed changes; project organization and task association become unreliable.

A screenshot captured immediately before restart exists and shows the newer state, but it contains work-related discussion and should be provided privately to OpenAI Support or maintainers on request, not attached publicly by default.

Possibly related public reports: #43434, #39121, #26236.

Begin by reproducing the Windows Desktop restart sequence described in the issue, comparing the visible transcript and project rename before shutdown with the state after reopening the same task. Done means the current conversation and project metadata survive a clean restart, or the app shows a clear recovery error and non-destructive recovery path instead of stale history.