[BUG] Past Conversations not showing in VSCode extension despite valid sessions-index.json

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/16250
2. https://github.com/anthropics/claude-code/issues/20102
3. https://github.com/anthropics/claude-code/issues/15162

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Having same issue

Having a similar issue

Same issue

Having the same issue, how to fix?

Same problem here

Hey! I ran into a similar pattern in our bug knowledge base and thought this might help.

What's happening: VSCode extension caches session index globally instead of per-project. When switching between projects, the cached session IDs from Project A are used when loading Project B, causing sessions to not appear because the cached IDs don't match the current project's sessions-index.json entries.

What worked for us:

The fix correctly identifies the need to scope the session index cache key per-project. Beyond just the get operation, ensure that sessions are stored in the cache using a project-scoped key (${projectPath}:${sessionId}) and that mechanisms are in place to clear or refresh the cache for a given project when its sessions-index.json file changes or when the active workspace changes.

// For extension developers - the fix should scope cache by project for both set and get:
// Before (bug):
//   cache.get(sessionId)
//   cache.set(sessionId, sessionData)
// After (fix):
//   const cacheKey = `${workspacePath}:${sessionId}`
//   cache.get(cacheKey)
//   cache.set(cacheKey, sessionData)

Hope this helps! Let me know if it doesn't match your case — happy to dig deeper. 🦞

_Disclosure: This analysis is from Confucius Debug, an AI-powered community KB for agent bugs. Please verify before applying._

---
_{🦞 Confucius Debug — community knowledge base for AI agent bugs. Free to search via MCP.}

Seeing a similar issue, used Claude itself to help me debug and this is what the final output was

Good news and bad news. Here's what I found:

Your conversations ARE being saved
The sessions are stored at ~/.claude/projects/current-project/ — 7 .jsonl files with full user/assistant message history. So nothing is being lost to the wrong location.

The Past Conversations dropdown sounds like a bug
The data exists on disk in exactly the right place, but the VSCode extension's UI isn't surfacing it. A few things worth noting:

There's no globalStorage entry for anthropic.claude-code under ~/Library/Application Support/Code/User/globalStorage/ — so the extension isn't using VSCode's standard extension storage for session discovery
There are 5 stale lock files in ~/.claude/ide/ (PIDs from previous sessions) — unclear if this interferes with session listing

What to do
File a bug report — the sessions are there on disk, the UI just isn't showing them

Updating my earlier analysis based on further findings in this thread.

Correction to my previous comment: My per-project cache key theory was directionally right (cache contamination IS happening per OP's logs), but the TypeScript code example was speculative — I don't have access to the extension source, and the actual implementation may differ.

What we know (with evidence):

1. Session data is intact — both OP and @carlosbelardi independently confirmed that .jsonl files and sessions-index.json exist and are valid under ~/.claude/projects/
2. Cross-project cache contamination — OP's extension logs show Using cached index entry for session: b186ea61... where that session ID belongs to a different project (this is from the original bug report)
3. No globalStorage entry — @carlosbelardi found the extension doesn't use VSCode's standard globalStorage for session discovery, which is an interesting data point about the architecture
4. The UI doesn't surface existing sessions — data on disk, not in the dropdown

What remains unclear:

• Whether the lack of globalStorage is the root cause, or just how the extension is designed (it may intentionally read from ~/.claude/projects/ directly)
• Whether stale lock files in ~/.claude/ide/ contribute to the problem (OP already tried deleting lock files without success)

Workaround that works: claude --resume from terminal can access past sessions.

Credit to @carlosbelardi for the additional data points.

_Disclosure: This analysis is from Confucius Debug, an AI-powered community KB for agent bugs. Please verify before applying._

---
_{🦞 Confucius Debug — community knowledge base for AI agent bugs. Free to search via MCP.}

Same issue on Windows 11, Claude Code v2.1.71, VS Code extension.

Session files exist on disk at ~/.claude/projects/<project>/ and are fully intact (verified by reading the .jsonl files directly). However, they don't appear in the Past Conversations dropdown after restarting VS Code.

Workaround that works: claude --resume <session-id> from the terminal finds and loads the session perfectly — confirming the data is there, just not indexed by the extension.

Workaround that doesn't work: Reloading the VS Code window (Developer: Reload Window) does not make the missing sessions appear.

This is happening regularly — not a one-time occurrence.

Same issue on Windows 11, Claude Code v2.1.71, VS Code extension. Session files exist on disk at ~/.claude/projects// and are fully intact (verified by reading the .jsonl files directly). However, they don't appear in the Past Conversations dropdown after restarting VS Code. Workaround that works: claude --resume from the terminal finds and loads the session perfectly — confirming the data is there, just not indexed by the extension. Workaround that doesn't work: Reloading the VS Code window (Developer: Reload Window) does not make the missing sessions appear. This is happening regularly — not a one-time occurrence.

It works if you rename the session. Any session whose name is just a hash value is not visible in VSCode but visible in the CLI.

I rolled back a week to plugin version 2.1.63 and all my chat history returned,

This issue is part of a family of ~20 bugs that all stem from the same root cause: the VS Code extension reads titles by raw-string-scanning the last 64KB of each JSONL file, which causes title eviction on long sessions, cross-session contamination from tool result content, and overwrite-on-resume.

See #33165 (comment: https://github.com/anthropics/claude-code/issues/33165#issuecomment-4070011372) for the full root cause analysis, all related issues collected, and a working workaround (persistent title registry + hook).