[BUG] Conversation History Loss

Resolved 💬 3 comments Opened Apr 9, 2026 by kazimanil Closed Apr 12, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Migration from Cursor to VSCode doesn't enable the chat history from Cursor.

Last prompts from Claude Code below:

The sessions directory got reset (likely when you restarted). The old index files are gone too — it seems Claude Code only keeps index entries for currently running sessions and cleans up old ones on restart.

This means /resume isn't designed to work from these index files for historical sessions. It likely reads the .jsonl files directly from the projects folder but may filter by some criteria.

Let me check what's different about the sessions that do/don't show:

All the files have the same format. The issue is likely that /resume in the VS Code extension only shows sessions that were started from VS Code (tracked via the live sessions/ index), and doesn't scan the .jsonl files directly.

This appears to be a limitation/bug in the Claude Code VS Code extension — it doesn't discover historical sessions from .jsonl files alone. I'd recommend filing this as an issue at https://github.com/anthropics/claude-code/issues.

Unfortunately, I can't make /resume pick them up since the extension controls that behavior internally and the session index files get cleaned up on restart.

What Should Happen?

I should be able to see the whole history of my chat with Claude listed.

Error Messages/Logs

Steps to Reproduce

Try migrating from Claude extension from VSCode to Cursor while keeping your chat history.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.97

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗