Codex Windows Desktop shows thread messages in reversed or scrambled order after restart

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

Unknown app version. Installed from Microsoft Store. Microsoft Store / winget reports no newer update available. 暂时没有找到具体版本号。通过 Microsoft Store 安装，Microsoft Store / winget 均提示暂无可用更新。

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Windows 11 Pro x64

What issue are you seeing?

Codex Windows Desktop displays historical thread messages in the wrong order after restarting the app.

The issue is not that the raw chat/session content is deleted. The problem appears to be in the Desktop app UI/session rehydration layer.

Observed behavior:

• After opening Codex, the project/thread list initially appears normal.
• After a short delay, while the app finishes loading local sessions, some thread titles change automatically.
• Opening affected threads shows messages in reversed or scrambled order.
• This happens across multiple projects and multiple threads.
• Some old threads also show unstable titles after the app finishes loading.
• Restarting Codex does not fix the issue.
• Microsoft Store / winget reports that no newer Codex version is available.
• I have already submitted in-app feedback with logs included.

Feedback ID:
019f2e50-b9ca-7e90-ac3e-3428a5e5edd6

This looks like a Codex Desktop local UI cache / thread index / session rehydration bug, not corrupted source project files.

中文说明：
Codex Windows 桌面版在关闭并重新打开后，历史聊天记录的显示顺序会出现倒序或错乱。

这个问题不是原始聊天内容被删除，也不像是项目文件损坏，更像是 Codex Desktop 在重新加载本地会话时，UI 缓存、线程索引或 session rehydration 出现了问题。

具体表现：

• 刚打开 Codex 时，左侧项目/线程列表看起来是正常的。
• 过一会儿，Codex 完成本地会话加载后，部分线程标题会自动变化。
• 点开受影响的线程后，聊天消息会倒序显示，或者顺序错乱。
• 这个问题影响多个项目和多个线程。
• 一些旧线程标题也会在加载后发生变化。
• 重启 Codex 无法解决。
• Microsoft Store / winget 均提示没有可用更新。
• 我已经通过 Codex 内置反馈提交过一次，并包含当前会话日志。

反馈 ID：
019f2e50-b9ca-7e90-ac3e-3428a5e5edd6

What steps can reproduce the bug?

Feedback ID: 019f2e50-b9ca-7e90-ac3e-3428a5e5edd6

What is the expected behavior?

_No response_

Additional information

_No response_