Cursor extension: Claude Code tab is visible but never initialises after reopening Cursor (must open a new tab, losing the live session)

Summary

When running the Claude Code extension inside Cursor (VSCode-based), quitting and reopening Cursor leaves the existing Claude Code tab/panel visually present but in a non-initialised / unresponsive state. It never reconnects to its session. The only way to get a working session back is to close that tab and open a brand-new Claude Code tab, which starts a fresh conversation — so the live, in-context session is lost (the on-disk transcript is still there and can be resumed manually, but the tab does not auto-recover).

Environment

• Host IDE: Cursor (VSCode-based)
• Claude Code: extension / native IDE integration
• OS: macOS (Darwin 25.3.0, Apple Silicon)

Steps to reproduce

1. Have an active Claude Code conversation open in a tab inside Cursor.
2. Quit Cursor completely.
3. Reopen Cursor.
4. Observe the previously-open Claude Code tab is still shown.

Expected

The tab reconnects/initialises and resumes the prior session (or clearly offers a one-click "resume").

Actual

The tab is present but never initialises — it appears dead/unresponsive. The user must close it and open a new tab, which begins a fresh session and drops the live context.

Impact

Loss of working context across IDE restarts; confusing because the tab looks alive. The transcript is recoverable via Session History / claude --resume, but the broken tab gives no indication of that and there is no auto-recovery.

Workaround currently used

Close the dead tab → open a new Claude Code tab → use Session history (or claude --resume / claude --continue in the integrated terminal) to reload the prior conversation.

Suggestions

• Auto-reconnect/resume the session a restored tab was attached to, or
• Show a clear "Resume previous session" affordance in a tab that failed to initialise, or
• Surface an error state instead of an apparently-alive-but-dead tab.