claude-code - 💡(How to fix) Fix VS Code extension: sessions missing from history dropdown (not indexed in history.jsonl) [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#60610Fetched 2026-05-20 03:54:04
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Author
Timeline (top)
labeled ×6commented ×2closed ×1

Sessions created in the VS Code extension are not appearing in the history dropdown. The session .jsonl files exist on disk but are not being appended to ~/.claude/history.jsonl, which the UI uses to populate the session list.

Root Cause

Sessions created in the VS Code extension are not appearing in the history dropdown. The session .jsonl files exist on disk but are not being appended to ~/.claude/history.jsonl, which the UI uses to populate the session list.

RAW_BUFFERClick to expand / collapse

Summary

Sessions created in the VS Code extension are not appearing in the history dropdown. The session .jsonl files exist on disk but are not being appended to ~/.claude/history.jsonl, which the UI uses to populate the session list.

Environment

  • Claude Code VS Code extension (latest as of 2026-05-19)
  • macOS (Darwin 25.4.0)
  • VS Code

Steps to reproduce

  1. Use Claude Code in VS Code over multiple sessions
  2. Click the history button to reveal the session dropdown
  3. Observe that recent sessions are missing

Diagnostic details

  • 10 session .jsonl files exist in ~/.claude/projects/<project>/
  • Only 4 of those 10 are indexed in ~/.claude/history.jsonl
  • 6 sessions (from May 11 through May 19) are invisible in the UI
  • The last indexed session is from May 11; all sessions after that are missing from the index
  • The session data is intact on disk, just not registered in the index

Possibly related actions

  • Renaming sessions via the UI around the time this started
  • Sessions also appearing in VS Code's native "Chat" history (possible interaction between the two systems)

Expected behavior

All sessions should appear in the history dropdown, regardless of whether they were renamed or how VS Code's native chat history interacts with them.

Actual behavior

Recent sessions are invisible in the dropdown. Data is not lost (files exist on disk), but the history.jsonl index is not being updated with new sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

All sessions should appear in the history dropdown, regardless of whether they were renamed or how VS Code's native chat history interacts with them.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix VS Code extension: sessions missing from history dropdown (not indexed in history.jsonl) [2 comments, 2 participants]