[BUG] timeout makes you loose session

Environment

• Platform (select one):
• [ ] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: <!-- output of claude --version -->
• Operating System: <!-- e.g. macOS 14.3, Windows 11, Ubuntu 22.04 -->
• Terminal: <!-- e.g. iTerm2, Terminal App -->

Bug Description

<!-- A clear and concise description of the bug -->
i'm on the $200 plan, so did not expect session to timeout.
claude code ask to edit. Took a break for a couple of days. When i cam back, got this timeout (see bottom). and session is lost. Kind of suck to loose your context for not being a heavy user.

Steps to Reproduce

1. <!-- First step -->
2. <!-- Second step -->
3. <!-- And so on... -->

Expected Behavior

<!-- What you expected to happen -->

Actual Behavior

<!-- What actually happened -->

Additional Context

<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Opened changes in Visual Studio Code ⧉ │
│ Save file to continue… │
│ │
│ Do you want to make this edit to files_and_directory.js? │
│ ❯ 1. Yes │
│ 2. Yes, and don't ask again this session (shift+tab) │
│ 3. No, and tell Claude what to do differently (esc) │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
... left it for a couple of days, when i came back ...

node:internal/process/promises:394
triggerUncaughtException(err, true / fromPromise /);
^

cF [McpError]: MCP error -32001: Request timed out
at Timeout.M (file:///home/john/.nvm/versions/node/v22.17.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1200:17327)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7) {
code: -32001,
data: { timeout: 100000000 }
}

Node.js v22.17.0