[Windows desktop app] Reopening a conversation hides later history even though the local session transcript still contains it

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

26.903.61454

What subscription do you have?

PLUS

What platform is your computer?

Windows 11

What issue are you seeing?

Summary

The Windows desktop app repeatedly fails to display the full history of a long-running Codex conversation after I reopen it.

The conversation view returns to an older point in the discussion. Later messages are missing from the displayed history, while newly submitted messages appear after that older content.

Importantly, read-only checks found references to later development work and test results in the local transcript for the same conversation. I cannot confirm that the underlying records have been deleted.

Environment

• Product: Codex in the Windows desktop app, not the IDE extension
• Desktop app version/build: [please fill in]
• Windows version/build: [please fill in]
• Workspace: Local software development project
• Conversation: A long-running conversation with many tool calls
• Observation date: September 13, 2026
• Time zone: UTC+8
• In-app feedback reference: [paste the reference returned after submission, if available]

Steps to reproduce

1. Open an existing long-running Codex conversation.
2. Continue working in it, including development, testing, and normal messages.
3. Leave the conversation and reopen the same conversation.
4. Inspect the displayed history.

In this affected conversation, reopening it repeatedly reproduces the problem.

Expected behavior

Previously saved messages should remain accessible after reopening the conversation.

If older messages are loaded incrementally, the app should allow them to load without leaving an unexplained gap in the conversation.

Actual behavior

The displayed history returns to an older development stage and omits subsequent discussion and results.

New messages can still be submitted and displayed, but reopening the conversation again does not reliably restore the missing history.

This is not a case of the entire conversation disappearing from the sidebar. The conversation remains accessible, but its contents are incomplete.

Read-only diagnostic observations

During assistant-assisted troubleshooting:

• The conversation-reading tool also returned an old development turn as the newest available turn.
• That old turn was reported as inProgress, despite later development and testing having taken place.
• Searches of the local JSONL transcript for the same conversation found references to later package creation and successful tests that were absent from the displayed history.

These observations suggest a possible history-loading, indexing, or session-reconstruction inconsistency, but the root cause has not been established.

The presence of later content in the transcript does not prove that every missing message is intact.

Possibly related symptom

During recent development sessions, I have also encountered interruptions with an error that appears to be aborted, sometimes accompanied by a prolonged lack of visible progress.

I do not yet have a complete error trace attached, and I cannot confirm whether this is related to the history-display issue. I can provide the exact error text and timestamp when it happens again.

Impact

This makes it difficult to review previous decisions, development results, and verification evidence, or to determine where work should resume.

Feedback and attachments

I have already submitted feedback through the desktop app.

Attached: A screenshot showing older conversation content followed by a recent message, with the intervening history missing.

The local transcript may contain private source code and sensitive project information, so I am not attaching the full unredacted file publicly.

Please advise which sanitized diagnostics are needed and how to recover the conversation display without deleting or resetting the existing session data.

What steps can reproduce the bug?

关闭窗口再打开就看不到之前的记录，但是codex说本地记录里是有记录，但是无法显示

What is the expected behavior?

No response

Additional information

No response

Start by investigating the Windows desktop conversation reopen and history-loading path, then compare the displayed history with the local JSONL transcript described in the report. No source files or tests are named, so identify the relevant entry points and request sanitized diagnostics for the affected session. Done means reopening the conversation consistently restores all available saved messages without unexplained gaps.