Linux desktop: earlier chat history unavailable despite retrievable saved turns

No source file, test, or deterministic reproducer is named. Start by investigating the Linux desktop app's conversation-history loading and the read-only task-history retrieval path described in the report; done means earlier saved turns reliably appear or a visible error and retry path is provided without requiring a restart.

Linux desktop app: earlier chat history unavailable despite retrievable saved turns

Problem and impact

During a long-running local conversation, I could not see the earlier chat
history in the Linux ChatGPT desktop app. I subsequently had to restart my
computer because of a bug in the app, interrupting the work and stopping local
services used by the task.

The exact cause of the missing history and the restart-triggering problem has
not been established. This is an observed incident, not a deterministic reproducer.

Environment

• Linux Mint 22.3 (Zena), Ubuntu Noble base.
• Installed desktop package: chatgpt 26.908.40834.
• Codex bundled with the desktop app: 0.154.0-alpha.6.2.
• Separately installed Codex CLI: 0.154.0 (listed separately to avoid confusing
  the CLI version with the desktop app's bundled runtime).
• Reported on 2026-09-20, America/Los_Angeles.

Observed sequence

1. Return to a long-running local conversation and attempt to view prior messages.
2. Earlier history is unavailable in the visible chat.
3. A read-only app-tool check still lists the same task. Reading the task returns
   completed older user/assistant turns and a pagination cursor indicating more
   history is available.
4. I reported needing a computer restart because of the app bug.
5. After restart, the task's local artifacts remain present, but temporary local
   processes must be restarted.

Expected behavior

Previously saved conversation turns should remain visible or load on demand.
The app should recover from a history-loading/display failure without requiring
a computer restart. If loading fails, a visible error and retry action would help.

Evidence boundaries

The read-only retrieval supports that at least the inspected earlier turns were
still persisted. It does not establish a root cause or prove that every earlier
turn is intact. No crash trace or reliable minimal reproducer has been captured.
Private conversation transcripts, credentials, network identifiers, and project
contents are not included in this report.

Additional support request

Could support please consider a courtesy usage-limit reset for the disruption
and recovery work? <3