Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Sessions appear empty in UI despite full message history existing on disk [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51934•Fetched 2026-04-23 07:41:00
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
SnapshotCiTySnapshotCiTy
Participants
SnapshotCiTySnapshotCiTy
Timeline (top)
labeled ×4closed ×1

In the Claude Code Desktop application (macOS), sessions frequently appear completely empty in the UI — no messages visible — even though the session has a title (auto-generated from conversation content) and the full message history exists in the corresponding .jsonl file on disk.

It is unclear whether this also affects the CLI tool.

Error Message

  1. Warn users before/after compaction that messages will be hidden

Root Cause

In the Claude Code Desktop application (macOS), sessions frequently appear completely empty in the UI — no messages visible — even though the session has a title (auto-generated from conversation content) and the full message history exists in the corresponding .jsonl file on disk.

It is unclear whether this also affects the CLI tool.

RAW_BUFFERClick to expand / collapse

Description

In the Claude Code Desktop application (macOS), sessions frequently appear completely empty in the UI — no messages visible — even though the session has a title (auto-generated from conversation content) and the full message history exists in the corresponding .jsonl file on disk.

It is unclear whether this also affects the CLI tool.

Steps to Reproduce

  1. Have an active session in the Claude Code Desktop app with multiple exchanges
  2. Return to the session later (or after compaction occurs)
  3. The session list shows the session with its AI-generated title
  4. Opening the session shows zero messages in the chat window

Expected Behavior

All messages should be visible, or at minimum the user should be clearly informed that compaction has occurred and offered a way to view the original history.

Actual Behavior

The chat window is blank. No indication that messages exist but are hidden. The only way to recover conversation history is to manually parse the raw .jsonl files at ~/.claude/projects/<project>/.

Impact

This affects most sessions. Users investing significant work into AI-assisted sessions lose access to their conversation history through normal use of the product — with no warning, no export option, and no UI affordance to recover it.

Environment

  • Platform: macOS (Darwin 24.6.0)
  • Claude Code Desktop application

Request

  1. Make compacted message history accessible from the UI (e.g. a "show full history" option)
  2. Warn users before/after compaction that messages will be hidden
  3. Provide a built-in export or history viewer

extent analysis

TL;DR

Implement a "show full history" option in the Claude Code Desktop application to make compacted message history accessible from the UI.

Guidance

  • Investigate the compaction process to understand how it affects message visibility in the UI, and consider modifying it to preserve message history or provide a clear indication of compaction.
  • Add a warning to inform users before or after compaction that messages will be hidden, to manage expectations and provide transparency.
  • Develop a built-in export or history viewer feature to allow users to access and review their conversation history, even if it's not visible in the main chat window.
  • Review the current UI design to identify potential areas for improvement, such as adding a button or menu option to access the full message history.

Example

No code snippet is provided as the issue does not contain specific technical details about the implementation.

Notes

The solution may require significant changes to the application's architecture and UI, and may involve trade-offs between performance, storage, and user experience. Additionally, the fix may not be applicable to the CLI tool, which is not fully described in the issue.

Recommendation

Apply a workaround by implementing a "show full history" option, as this provides a clear and immediate solution to the problem of inaccessible message history, and can be developed and tested independently of other features.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#conversation history#memory optimization#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Sessions appear empty in UI despite full message history existing on disk [1 participants]