Frequent session crashes on Windows (30+ in 2 days)

Resolved 💬 3 comments Opened Feb 23, 2026 by bonskari Closed Feb 27, 2026

Frequent session crashes on Windows (30+ in 2 days)

Description

Claude Code sessions crash frequently on Windows — over 30 crashes in the past 2 days. The session simply dies mid-conversation with no error message or stack trace. This happens during normal usage (reading files, spawning background agents, git operations).

Environment

  • Claude Code version: 2.1.50
  • OS: Windows 11 Pro (Build 26200, version 10.0.26200)
  • Shell: MSYS2/MINGW64 bash (3.3.6-341.x86_64)
  • Node.js: v22.17.0
  • Model: Claude Opus 4.6

Reproduction

No single trigger identified. Crashes occur across various activities:

  • During background agent execution (Task tool with run_in_background: true)
  • During normal file reads and git operations
  • Mid-conversation with no tool calls active
  • Sometimes immediately after a tool result returns

Usage pattern that may be relevant

  • Large monorepo (Flutter + Serverpod + Dart)
  • Multiple MCP servers configured (Playwright, Chrome DevTools, screen-capture, windows-screenshots)
  • Frequent use of background agents (worktree isolation)
  • Git worktrees active under .claude/worktrees/
  • Long-running sessions with substantial context

Impact

  • Severe workflow disruption — every crash requires re-establishing context
  • Background agents lose their work if they haven't committed
  • ~15+ crashes per day makes sustained work very difficult

Expected behavior

Sessions should remain stable for extended use, or at minimum provide an error message / crash log when terminating unexpectedly.

Additional context

No crash logs found in ~/.claude/logs/. The session terminates silently — the terminal just returns to the prompt with no error output. There is no opportunity to see what went wrong.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗