Desktop App: paginated thread history is replaced by a single interrupted initial turn after update

What variant of Codex are you using?

Codex Desktop App on Windows 11, signed in through a ChatGPT account.

Summary

After a recent Desktop App update, previously completed tasks can open with only their first user message and a partial initial assistant response. The displayed turn is marked interrupted and no further history is available.

This is not lost rollout data: the canonical local JSONL for the same task contains the full completed conversation and tool activity.

Reproduction pattern

1. Use Codex Desktop for a multi-turn task, including tool use and delegated tasks.
2. Let the task complete or continue it across several turns.
3. Update/restart Codex Desktop.
4. Reopen the existing task.
5. Observe that the UI shows only the initial turn as interrupted; there is no available older/newer page.

Observed on two independent tasks.

Expected behavior

Completed tasks should display their complete historical turns after a Desktop App update or restart.

Actual behavior

The Desktop UI / thread reader returns only the first fragment of the conversation:

• first user message;
• partial first assistant message;
• turn status interrupted;
• no additional history (hasMore=false).

Local evidence (redacted and aggregate-only)

For two affected Desktop tasks, the corresponding canonical rollout JSONL files parse cleanly and contain:

• task A: 18 user messages, 42 assistant messages, 15 completed turns;
• task B: 13 user messages, 67 assistant messages, 9 completed turns.

Both affected threads use history_mode=paginated. A comparable unaffected current Desktop thread uses legacy history. The primary local SQLite state passes integrity checks, and its rollout paths/timestamps match the complete JSONL files.

No raw prompts, credentials, project names, local paths, or thread IDs are included here.

Related issue

This looks like the Desktop/App manifestation of openai/codex#37577, which reports the same completed-rollout-to-interrupted reconstruction failure through CLI resume/app-server. The difference here is that it is visible directly in Codex Desktop UI after an update.

User feedback: Linux and Remote also show truncated paginated history

• Source: https://github.com/openai/codex/issues/40342
• Source: https://github.com/openai/codex/issues/40342#issuecomment-5393483353
• Source: https://github.com/openai/codex/issues/40342#issuecomment-5409222951
• Source: https://github.com/openai/codex/issues/40342#issuecomment-5409937838
• Type: external
• User reports:
  • “Reproduces across Linux Desktop, laptop Remote, and mobile Remote.”
  • “the Desktop/thread reader returns only one interrupted turn and reports no additional page” while the rollout contains later completed turns.
  • On a remote Ubuntu 24.04 host, “24/24 paginated-history threads have incomplete projections” and “The affected rollout files remain present and valid.”

Start at the Desktop thread reader and the paginated-history reconstruction path, comparing its projection with the canonical rollout JSONL and SQLite state described in the report. Done means reopened tasks retain all completed historical turns, show the correct status, and report additional pages when history exists; compare behavior with the related CLI/app-server issue and issue 40342.