Detailed Analysis
A Reddit user running Claude Desktop on Windows encountered a data-visibility discrepancy after reinstalling the application: while their standard Claude chat history restored normally upon sign-in, all Claude Code sessions vanished from the Desktop sidebar. Notably, the underlying data was not actually lost. The user confirmed that running `claude --resume` from the command line still surfaced the prior sessions, and the local `.claude` directory—including the `projects` and `sessions` subfolders and `history.jsonl`—remained fully intact on disk. This points to a disconnect between where Claude Code's CLI reads session transcripts and how Claude Desktop's sidebar indexes and displays that same data, rather than any actual deletion of user work.
The technical root of the issue likely lies in how Claude Desktop maintains its own local index or database reference to session metadata, separate from the raw JSONL transcript files that the CLI reads directly from `~/.claude/projects/`. When Desktop is reset or reinstalled, it appears to rebuild its internal state from a fresh sync with the user's account rather than rescanning the local filesystem for pre-existing session artifacts. The CLI, by contrast, appears to treat the JSONL files themselves as the source of truth, making it resilient to Desktop-level resets. This bifurcation—one client relying on account-synced session pointers and the other on raw local file discovery—creates a scenario where data integrity is preserved but discoverability through the primary GUI is broken.
This matters because Claude Code has increasingly become a core part of Anthropic's developer-facing product suite, and session continuity is essential for engineers who rely on long-running, context-heavy coding sessions. Losing visibility into past work, even temporarily or cosmetically, undermines trust in the tool's reliability, particularly for professional workflows where session history functions as an audit trail or reference for iterative development. The fact that recovery was possible only through CLI commands rather than through the Desktop UI also highlights a usability gap: casual or non-technical users who don't know to fall back on `claude --resume` might reasonably assume their work was permanently deleted, generating unnecessary support burden and eroding confidence in the desktop client specifically.
More broadly, this incident reflects a common growing pain in multi-client software architectures where a CLI and a GUI application share a local data store but maintain separate indexing or state-management layers. As Anthropic continues to expand Claude Code across platforms—desktop, CLI, IDE integrations, and potentially web—ensuring consistent, unified session state across these surfaces will be critical to avoiding similar fragmentation. The unanswered questions in the original post, particularly around whether this is specific to the Windows Store/MSIX packaging of Claude Desktop, also suggest platform-specific packaging or sandboxing behaviors (such as MSIX's isolated storage model) could be contributing factors, an issue Anthropic would need to address as it hardens the Windows distribution of its developer tools alongside its more mature macOS and Linux counterparts.
Read original article →