CRITICAL: Conversations disappear when closing VSCode or navigating away
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 16 comments · opened Feb 8, 2026
Description
Conversations are completely disappearing and becoming unrecoverable when:
- Closing and reopening VSCode
- Navigating to the chat summary page and returning to a conversation
- Switching between conversations
The chat history is lost with no way to recover it. This makes it impossible to maintain long-running development sessions.
Reproduction Steps
- Start a conversation in Claude Code
- Work for a while (multiple exchanges)
- Close VSCode or navigate to chat summary page
- Reopen VSCode or return to the conversation
- Expected: Conversation history is preserved
- Actual: Conversation is gone, completely vanished
Impact
- Severity: CRITICAL - Work cannot be persisted across sessions
- Blocker: Prevents any meaningful development work
- Frequency: 100% reproducible - happens every time
Environment
- OS: Windows (win32)
- Date: 2026-02-08
- Branch: hdfc-skr-snapshot (finance_app)
Current Workaround
Users are forced to manually create git backups of entire conversation transcripts after each session, which is not a sustainable solution.
Expected Behavior
Claude Code conversations should persist automatically and be fully recoverable when:
- Reopening VSCode
- Returning from chat summary
- Switching between active conversations
This is a core feature that should "just work".
16 Comments
Please fix.
Yes, it's quite bad and very annoying.
We're experiencing this across multiple enterprise users on Windows/VSCode. Conversation persistence is a hard requirement for our workflows, and the current behavior is blocking adoption for longer development tasks. Happy to provide logs or assist with testing a fix if that would be helpful.
I am also experiencing this problem. I lose 1 chat every time i close Claude code. I believe it is the one I have worked on most recently, which is obviously extremely frustrating. I have also noticed that VSCode chats do not keep their name changes most of the time. Unsure if it is a symptom of the same problem, or a separate problem.
Same here. Very frustrating. I have just lost an important conversation after 2 hours of debugging. I am on Linux and it does not happen all the time.
I threw Claude at this and sorted out a fix by patching the vs code extension JS. Works for me on Windows 11, hopefully it works for others.
It adds a fallback path for history/session loading:
.jsonlfiles directly from~/.claude/projects/<mapped-cwd>/.<sessionId>.jsonl.ai-titlerecords (or first user text).Patch file:
~/.vscode/extensions/anthropic.claude-code-2.1.101-win32-x64/extension.jsReplace the entire
listSessions()method with:Replace the entire
getSession(K)method with:Then run:
Developer: Reload Windowor restart VS CodeSame Problem. Windows 11 with WSL editing in Linux Ubuntu. Using the IDE, not the terminal.
Been happening for ages. Very annoying.
same problem after 5 months of this PR.
still also happening for me
Hello, I'm wondering if there is any updates on this? This is a critical issue for me, please let me know if there is anything information I can provide to help diagnose the problem. Even on Developer: Reload Window all of my chats disappear. New chats don't produce output from models, and the chat sessions tab shows thousands of line changes even though no code change has occurred.
<img width="994" height="2003" alt="Image" src="https://github.com/user-attachments/assets/735d0721-d892-4178-bbc0-48faad3e0c4f" />
21 sessions on disk, only 2 shown in panel
Hey AntonR-github, 21
.jsonlsessions on disk with only two visible in the VS Code panel sounds like the extension's session-list cache has dropped entries, rather than the transcript files being missing.I built
BasedGPT/claude-code-session-recoverywith a read-onlydiagnose.pyroute for this case. Runpython tools/diagnose.pyfirst and follow the exact command it prints. For the VS Code panel gap, the guarded path isrecover_vscode_sessions.pyin a dry run. Review what it proposes before applying it, and keep VS Code fully closed for any write step.Hope this helps, if my tools are able to help you, would appreciate a ⭐ :)
It’s still going on, which is really frustrating.
Please please, can we have someone fix this? This is super annoying!
This issue seems to be fixed for me now tied to a VSCode update:
https://github.com/microsoft/vscode/issues/328736#issuecomment-5430874462
Not sure if it's still affecting others.