Claude Code exits without warning mid-session (Windows)
Resolved 💬 3 comments Opened Apr 18, 2026 by vrgodev Closed Apr 21, 2026
Description
Claude Code exited without warning in the middle of an active session. No error message, no crash dialog — the process just terminated silently.
Environment
- OS: Windows 10 Pro 10.0.19045
- Shell: bash (Git Bash)
- Model: Claude Opus (claude-opus-4-6)
- Claude Code version: Latest (as of 2026-04-18)
What was happening
- Working inside a Tauri v2 + Rust + React project (desktop app)
- Executing a GSD workflow phase plan (phase 04, plan 06)
- Mid-way through applying code changes across ~17 files (TypeScript, Rust, HTML, JSON)
- Session had been running for a while with heavy tool use (file reads, edits, bash commands)
Impact
- Session context lost entirely — had to resume manually in a new conversation
- No data loss thanks to git working tree preserving uncommitted changes
- User had to reconstruct what was in-flight by inspecting
git diff
Expected behavior
- If Claude Code needs to exit, it should display a clear error/reason
- Ideally, session state should be recoverable (the session resume mechanism exists but wasn't triggered since exit was abrupt)
Steps to reproduce
Not reliably reproducible — happened once during a long session with heavy file editing across a Tauri project.
Additional context
The session was doing substantial multi-file edits (426 additions, 319 deletions across 17 files) as part of a planned workflow. The work was coherent and nearly complete when the exit occurred, suggesting it wasn't caused by a code generation error but rather an infrastructure/process issue.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗