VSCode extension: tabs lost on transient API/network outages

Problem

When using the Claude Code VSCode extension, any transient disruption — API outage, network blip, or brief connectivity loss — kills the active tab entirely. The conversation, scroll position, and flow are all lost.

This happens frequently enough that it disrupts workflow, especially during periods of intermittent API instability.

Expected behavior

The extension tab should survive transient outages and automatically reconnect when service is restored, similar to how other VSCode extensions (e.g., Remote SSH, Live Share) handle temporary disconnections with retry logic rather than terminating the session.

Current workaround

Using /resume to reload the last conversation after opening a new tab. This works but:

• Loses the tab itself (position in editor layout, any side-by-side arrangement)
• Breaks flow — requires manual intervention every time
• Doesn't restore mid-stream responses that were in progress

Feature request

• Graceful handling of connection drops with automatic retry/reconnect
• Preserve the tab and conversation state through transient outages
• Show a "reconnecting..." indicator instead of killing the tab