[DOCS] VS Code docs omit large-session resume unresponsiveness recovery guidance

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/vs-code
https://code.claude.com/docs/en/troubleshooting
https://code.claude.com/docs/en/sessions

Section/Topic

VS Code Resume past conversations and troubleshooting guidance for resuming large sessions.

Current Documentation

The VS Code docs say:

Click the Session history button at the top of the Claude Code panel to access your conversation history. You can search by keyword or browse by time (Today, Yesterday, Last 7 days, etc.). Click any conversation to resume it with the full message history.

The troubleshooting docs cover generic CLI hangs:

If Claude Code seems unresponsive: 1. Press Ctrl+C to attempt to cancel the current operation 2. If unresponsive, you may need to close the terminal and restart Restarting doesn't lose your conversation. Run claude --resume in the same directory to pick the session back up.

What's Wrong or Missing?

Claude Code v2.1.187 fixed the VS Code extension becoming unresponsive when resuming a large session, but the VS Code and troubleshooting docs do not mention what users should expect or do when a large VS Code session resume appears stalled or unresponsive.

Existing hang guidance is terminal-focused and does not cover the VS Code extension session history flow.

Suggested Improvement

Add a short VS Code-specific troubleshooting note:

If the VS Code extension appears unresponsive while resuming a large session, update to Claude Code v2.1.187 or later. Large sessions may take longer to load because the extension restores the full message history. If the panel remains stuck, reload the VS Code window and resume the session again from Session history.

Impact

Medium - Makes feature difficult to understand

Additional Context

v2.1.187 changelog context: [VSCode] Fixed extension becoming unresponsive when resuming a large session.

Duplicate search found related but not duplicate issues: #40122 for VS Code Not responding status guidance, #38580 for the VS Code red spinner after backend timeout, and #66618 for VS Code integrated-terminal inherited-env transcript/resume behavior. No open issue covers VS Code extension unresponsiveness specifically when resuming a large session.