claude-code - 💡(How to fix) Fix VSCode extension v2.1.101: session .jsonl files only contain ai-title, no conversation content [1 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#47089Fetched 2026-04-13 05:41:47
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Participants
Timeline (top)
labeled ×6

After updating the VSCode extension to v2.1.101 (installed 2026-04-11), all new conversation sessions only persist the ai-title entry to the .jsonl file. No user, assistant, file-history-snapshot, or other message types are written. Previous sessions (created with v2.1.92 and earlier) have full conversation data.

Root Cause

After updating the VSCode extension to v2.1.101 (installed 2026-04-11), all new conversation sessions only persist the ai-title entry to the .jsonl file. No user, assistant, file-history-snapshot, or other message types are written. Previous sessions (created with v2.1.92 and earlier) have full conversation data.

Code Example

$ wc -l 076fa6e7-*.jsonl
120 076fa6e7-bfd9-4baa-8339-9c97c839a712.jsonl

$ python3 -c "..."  # types: file-history-snapshot, queue-operation, user, last-prompt, ai-title, assistant, attachment

---

$ cat 349d9334-*.jsonl
{"type":"ai-title","sessionId":"349d9334-19e4-477b-a628-c5f4d667046e","aiTitle":"Evidence-based learning system with agent design"}
RAW_BUFFERClick to expand / collapse

Description

After updating the VSCode extension to v2.1.101 (installed 2026-04-11), all new conversation sessions only persist the ai-title entry to the .jsonl file. No user, assistant, file-history-snapshot, or other message types are written. Previous sessions (created with v2.1.92 and earlier) have full conversation data.

Steps to reproduce

  1. Update Claude Code VSCode extension to v2.1.101
  2. Start a new conversation in VSCode
  3. Have a multi-turn conversation with tool use
  4. Close the conversation
  5. Reopen it — title is visible but content is empty

Evidence

Session files in ~/.claude/projects/<project>/:

Old session (v2.1.92, working):

$ wc -l 076fa6e7-*.jsonl
120 076fa6e7-bfd9-4baa-8339-9c97c839a712.jsonl

$ python3 -c "..."  # types: file-history-snapshot, queue-operation, user, last-prompt, ai-title, assistant, attachment

New session (v2.1.101, broken):

$ cat 349d9334-*.jsonl
{"type":"ai-title","sessionId":"349d9334-19e4-477b-a628-c5f4d667046e","aiTitle":"Evidence-based learning system with agent design"}

All 6 sessions created on 2026-04-12 show the same pattern: 1 line, only ai-title, ~130 bytes. All sessions before 2026-04-11 have full content (50KB–6MB).

Environment

  • macOS Darwin 25.4.0 (Apple Silicon)
  • VSCode (latest)
  • Extension versions installed:
    • anthropic.claude-code-2.1.89-darwin-arm64 (Apr 1)
    • anthropic.claude-code-2.1.92-darwin-arm64 (Apr 7)
    • anthropic.claude-code-2.1.101-darwin-arm64 (Apr 11) ← broken
  • ~/.claude/sessions/ directory is empty
  • Custom hooks configured in settings.json (PreToolUse, PostToolUse, PostCompact, Stop) — but hooks don't interact with session persistence

Related

Possibly related to #46683 (2.1.101 /resume regression), though that issue is about cross-repo session visibility, not missing content.

extent analysis

TL;DR

Downgrade the VSCode extension to v2.1.92 to potentially restore full conversation data persistence.

Guidance

  • Verify that the issue is specific to the v2.1.101 extension version by checking if other users with the same version are experiencing similar problems.
  • Check the release notes for v2.1.101 to see if there are any known issues or changes related to conversation session persistence.
  • Test if the issue persists when creating a new conversation with the v2.1.101 extension, but without using any custom hooks or settings.
  • Consider reporting the issue to the extension developers, providing detailed steps to reproduce and evidence, such as the session files and system environment.

Example

No code snippet is provided as the issue seems to be related to the extension version rather than a specific code implementation.

Notes

The issue may be specific to the v2.1.101 extension version, and downgrading to a previous version may resolve the problem. However, this may not be a permanent solution, and it is recommended to wait for an official fix or update from the extension developers.

Recommendation

Apply workaround: Downgrade to v2.1.92, as it is the last known working version, to restore full conversation data persistence until a fixed version is released.

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…

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 VSCode extension v2.1.101: session .jsonl files only contain ai-title, no conversation content [1 participants]