[Workflow] Recover Claude Desktop's Empty Recents List After Reinstall (Windows)
Recover Claude Desktop's Empty Recents List After Reinstall (Windows)
Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging
Original source: r/ClaudeAI post/comment
What problem this solves
Claude Desktop's 'Code tab Recents' list is empty after a reinstall on Windows, preventing access to previous conversations through the GUI, even though the underlying conversation data is intact.
Summary
This workflow provides a workaround to restore old Claude Desktop sessions to the 'Recents' list after a reinstall. It involves creating a new, trusted throwaway session within the app, then quitting Claude Desktop and overwriting the content of the new session's underlying .jsonl file with the content of an old, desired session's .jsonl file. This leverages the app's trust in its own index entries while allowing the content to be swapped.
Why it is useful
This workflow is valuable because it solves a specific, frustrating, and common problem for Claude Desktop users on Windows: the loss of access to past conversations via the GUI after a reinstall. It provides a clear, step-by-step, and validated workaround that is safe for user data, offering a practical solution until an official fix is implemented.
Workflow
- Open a new, trivial session in the Claude Desktop Code tab to generate a trusted index entry.
- Identify the filename of the newly created .jsonl file for this throwaway session using PowerShell (e.g., Get-ChildItem 'C:\Users<you>.claude\projects<your-project-folder>*.jsonl' | Sort-Object LastWriteTime -Descending | Select-Object -First 1).
- Fully quit Claude Desktop, ensuring no Claude processes are running (e.g., Get-Process | Where-Object { $_.ProcessName -like 'Claude' }).
- Overwrite the content of the new throwaway session's .jsonl file with the content of your old desired session's .jsonl file, keeping the throwaway file's original name (e.g., Copy-Item 'C:\Users<you>.claude\projects<your-project-folder><OLD-session-id>.jsonl' 'C:\Users<you>.claude\projects<your-project-folder><NEW-throwaway-id>.jsonl' -Force).
- Relaunch Claude Desktop and click the tile for the throwaway session; it will now display your old conversation.
- Repeat the process for each old session you wish to recover in the Recents list.
Tools / artifacts
- Claude Desktop application
- Windows PowerShell
- .jsonl conversation files (C:\Users<you>.claude\projects<project-folder>*.jsonl)
- Claude Desktop index files (%APPDATA%\Claude\claude-code-sessions<accountId><orgId>\local_<sessionId>.json)
Validation signals
- Author describes failed attempts (manual index creation) and explains why they didn't work (internal validation check).
- Author provides a clear explanation of 'Why this works' based on observed application behavior (index validation vs. content reading).
- Author confirms the safety of the process, stating original .jsonl files are never modified.
- Author notes an alternative (claude --resume) for terminal users, indicating a clear understanding of the problem scope.
Cautions
- The workflow explicitly states that original .jsonl files are used as read-only source data and are never at risk of modification or deletion.
- Instructions include fully quitting Claude Desktop before file operations to prevent potential data corruption or file locking issues.
Limitations
- This is a workaround for a bug, not an official fix, and may become obsolete with future Claude Desktop updates.
- The process needs to be repeated manually for each old session a user wishes to recover.
- Sidebar titles for recovered sessions will not auto-update to reflect the old conversation's title.
- Specific to Windows operating system.
Rate this workflow
Upvote this post if the workflow is useful, reproducible, or worth recommending.
Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.
Reply if it worked for you, failed, is outdated, or has a better alternative.
This post was generated automatically from the workflow library database.
Posted Jun 30, 2026, 2:48 AM UTC