Skip to content

[BUG] timeout makes you loose session #4810

Description

@johngrabner

Environment

  • Platform (select one):
    • Anthropic API
    • AWS Bedrock
    • Google Vertex AI
    • Other:
  • Claude CLI version:
  • Operating System:
  • Terminal:

Bug Description

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

Expected Behavior

Actual Behavior

Additional Context

╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 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

Activity

  1. github-actions commented on Dec 6, 2025

    @github-actions

    This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

  2. github-actions commented on Jan 6, 2026

    @github-actions

    This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

  3. github-actions commented on Jan 14, 2026

    @github-actions

    This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.

  4. locked as resolved and limited conversation to collaborators on Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:mcpautocloseIssue will be closed automaticallybugSomething isn't workingmemory

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions