Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Conversation history no longer persists after Developer: Reload Window in VS Code

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…

Conversation history used to persist after using Developer: Reload Window in VS Code. As of today (2026-05-15), the conversation is cleared on reload instead of being restored.

Root Cause

Conversation history used to persist after using Developer: Reload Window in VS Code. As of today (2026-05-15), the conversation is cleared on reload instead of being restored.

RAW_BUFFERClick to expand / collapse

Description

Conversation history used to persist after using Developer: Reload Window in VS Code. As of today (2026-05-15), the conversation is cleared on reload instead of being restored.

Steps to Reproduce

  1. Start a conversation with Claude Code in VS Code
  2. Use Developer: Reload Window (or Ctrl+Shift+P → "Developer: Reload Window")
  3. Observe that conversation history is gone

Expected Behavior

Conversation history should be restored after the window reloads, as it did previously.

Actual Behavior

Conversation history is completely lost after reload.

When Did It Stop Working

  • Last working: 2026-05-14
  • First broken: 2026-05-15 (likely due to an overnight auto-update)

Environment

  • OS: macOS (Darwin 25.5.0)
  • IDE: VS Code with Claude Code extension

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…
#conversation history#callback error#memory management#API rate limit#retriever error

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 Conversation history no longer persists after Developer: Reload Window in VS Code