VSCode extension: conversations disappear from history/search

Resolved 💬 3 comments Opened Mar 24, 2026 by Poojan-AI Closed Mar 28, 2026

Description

Conversations that exist on disk (as .jsonl files in ~/.claude/projects/) are not discoverable through the VSCode extension's conversation history UI. Searching by conversation name returns no results even though the data is intact.

Steps to Reproduce

  1. Have an existing conversation with a name (e.g., "Aurora")
  2. Close the conversation
  3. Try to find it later using the VSCode extension's conversation history/search
  4. The conversation does not appear in the list or search results

Expected Behavior

All conversations stored on disk should be searchable and resumable from the VSCode extension UI.

Actual Behavior

The conversation files exist in ~/.claude/projects/<project>/ as .jsonl files, but they don't show up in the extension's conversation picker or search. The only workaround is to manually find the conversation UUID from the filesystem and resume via CLI (claude --resume <uuid>).

Environment

  • VSCode extension (latest)
  • Windows 11 Pro
  • Model: Claude Opus 4.6 (1M context)

Impact

This is a recurring frustration — users lose track of important conversations and assume data has been lost, when it's actually a UI/indexing issue. Conversation history should be reliable and searchable.

View original on GitHub ↗

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