claude-code - 💡(How to fix) Fix [BUG] Claude Desktop history entries render blank when session metadata is missing cliSessionId [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#56172Fetched 2026-05-05 05:56:19
View on GitHub
Comments
0
Participants
1
Timeline
10
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×8labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this specific failure mode does not appear to be documented yet
  • This is a single bug report
  • I am using a current Claude Desktop / Claude Code install

What's Wrong?

Claude Desktop can show old Code/Cowork sessions in the history picker, but clicking one opens a blank conversation pane or an indefinite loading state when the Desktop metadata file exists but is missing cliSessionId.

This is different from the already-reported cases where all metadata is missing after a migration, or where MSIX leaves files stuck as .json.tmp. In this case the local_<uuid>.json metadata file is present and readable, so the picker entry appears, but Desktop has no bridge to the actual CLI transcript JSONL.

Observed local architecture:

extent analysis

TL;DR

The issue can be resolved by ensuring the cliSessionId is present in the Desktop metadata file, which is necessary for bridging to the actual CLI transcript JSONL.

Guidance

  • Verify that the cliSessionId field exists in the local_<uuid>.json metadata file and contains a valid value.
  • Check the metadata file's format and content to ensure it matches the expected structure, which should include the cliSessionId field.
  • If the cliSessionId is missing, investigate why it was not written to the metadata file during the session creation process.
  • Consider adding error handling or logging in the code that handles session creation and metadata file writing to help diagnose similar issues in the future.

Notes

The solution assumes that the cliSessionId is required for the conversation pane to load correctly. Without more information about the code or the expected behavior, it's difficult to provide a more specific fix.

Recommendation

Apply workaround: manually add the cliSessionId to the metadata file or modify the code to handle cases where the cliSessionId is missing, as the root cause of the issue is likely related to the missing cliSessionId field.

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…

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 [BUG] Claude Desktop history entries render blank when session metadata is missing cliSessionId [1 participants]