Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Multi-agent setup (6-8 windows) causing repeated system crashes on Windows -- v2.1.118 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52495•Fetched 2026-04-24 06:05:39
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
ThatDragonOverThereThatDragonOverThere
Participants
github-actions[bot]github-actions[bot]ThatDragonOverThereThatDragonOverThere
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

Running a multi-agent Claude Code setup (1 Opus PM + 6-8 Sonnet worker windows) on Windows causes repeated full system crashes. Crashes require full restart of all agent windows and interrupt overnight autonomous pipeline runs.

Root Cause

Running a multi-agent Claude Code setup (1 Opus PM + 6-8 Sonnet worker windows) on Windows causes repeated full system crashes. Crashes require full restart of all agent windows and interrupt overnight autonomous pipeline runs.

RAW_BUFFERClick to expand / collapse

Summary

Running a multi-agent Claude Code setup (1 Opus PM + 6-8 Sonnet worker windows) on Windows causes repeated full system crashes. Crashes require full restart of all agent windows and interrupt overnight autonomous pipeline runs.

Environment

  • OS: Windows
  • Claude Code: v2.1.118
  • Setup: 1 Opus window (PM/coordinator) + 6-8 Sonnet windows (workers)
  • Coordination: filesystem handshake files (.claude/handshake/)
  • Runtime: overnight autonomous runs (8+ hours)

Behavior

System crashes repeatedly during sustained multi-agent operation. Each crash requires:

  • Full system restart
  • Manual relaunch of all 6-8 agent windows
  • Re-approval of permission prompts in each window (compounded by #37442)
  • Manual check of which pipeline steps completed before crash

Suspected contributors

  1. Orphaned subagent processes not releasing resources after task completion (related: #51860, #52016)
  2. Sustained disk I/O from continuous parquet writes + agent context writes to ~/.claude/projects/
  3. Memory pressure from 6-8 simultaneous large-context sessions (each loading ~200KB CLAUDE.md per turn)
  4. CPU load from permission prompt polling when #37442 blocks workers

Impact

Overnight autonomous runs cannot complete reliably. Every crash loses 1-3 hours of pipeline progress and requires manual intervention -- defeating the purpose of autonomous operation.

Request

  • Memory and CPU profiling of multi-window Claude Code setups on Windows
  • Resource limits or warnings when total Claude Code process memory exceeds threshold
  • Graceful checkpoint on crash so sessions can resume without full manual restart

extent analysis

TL;DR

Implementing resource limits and monitoring for the Claude Code setup may help prevent system crashes by mitigating memory pressure and high disk I/O.

Guidance

  • Investigate the suspected contributors to system crashes, such as orphaned subagent processes, sustained disk I/O, memory pressure, and CPU load, to identify the primary cause.
  • Consider implementing a monitoring system to track memory and CPU usage of the Claude Code processes to detect potential issues before they lead to crashes.
  • Explore options for implementing resource limits or warnings when total Claude Code process memory exceeds a certain threshold to prevent overloading the system.
  • Develop a graceful checkpointing mechanism to allow sessions to resume without full manual restart in case of a crash.

Example

No specific code snippet can be provided without further information on the Claude Code setup and its internal workings.

Notes

The provided information suggests that the issue is complex and multifaceted, requiring a thorough investigation of the system's behavior and performance under load. The suggested steps are intended to help mitigate the issue, but may not provide a complete solution.

Recommendation

Apply a workaround by implementing resource monitoring and limits to prevent overloading the system, as this is a more feasible short-term solution compared to upgrading to a potentially non-existent fixed version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Multi-agent setup (6-8 windows) causing repeated system crashes on Windows -- v2.1.118 [1 comments, 2 participants]