Conversation history disappears after quitting and relaunching the app (session continues correctly server-side, but transcript is not shown)

Environment

• OS: macOS 26.6.1 (build 25G76)
• Client: Claude Code (desktop app; unable to determine exact version — claude --version is not available from this app's shell, please advise how to find it)

Summary

During a single long-running work session, I quit the app and relaunched it several times over the course of the conversation. Each time, the conversation continued to work correctly in the sense that Claude retained full context of everything discussed earlier (it could reference prior decisions, files created, etc. accurately). However, the visible transcript in the app UI no longer showed the earlier messages after relaunch — only messages from the point of relaunch onward were displayed.

This happened at least twice within the same session.

Steps to reproduce

1. Start a long conversation with Claude Code (many turns, spanning a substantial amount of work).
2. At some point mid-session, quit the app entirely.
3. Relaunch the app (the same conversation/session appears to resume, since Claude still has full context).
4. Scroll up in the transcript to view earlier turns from before the quit.

Expected behavior

The full conversation transcript, including turns from before the app was quit, should remain visible/scrollable after relaunching.

Actual behavior

Only messages from after the relaunch are visible in the transcript. Earlier turns are missing from the UI, even though the underlying assistant clearly still has that context (verified by asking it to recall specific details from before the restart, which it could do correctly).

Impact

Users cannot review or refer back to earlier parts of a long session after restarting the app, even though nothing was actually lost server-side. This is confusing and makes it hard to trust that work/decisions from earlier in the session are preserved, even though functionally they are (from the assistant's side).

Additional notes

This was reported to me (the assistant) by the user directly inside the affected session. The user set up GitHub CLI (gh) authentication themselves and asked me to file this report on their behalf using their account, since they were unfamiliar with GitHub.