Investigate: VS Code crash during Squad execution

[bradygaster]

Summary

User reports VS Code unexpectedly closes (no crash dialog) while Squad is executing a task. Needs investigation to determine if Squad's resource footprint contributes.

Origin: Discussion #174 by @diberry

Context

• VS Code nightly build
• No crash dialog — VS Code just closes
• Happened during Squad task execution

Investigation Plan

1. Audit Squad's memory footprint during multi-agent execution
2. Check file watcher count (VS Code has limits)
3. Review process spawning patterns
4. Test on stable VS Code vs nightly
5. Check if terminal flicker fix (Fix terminal flickering — raw ANSI escape codes bypass Ink render system #254) reduces resource pressure

Related

• Terminal flickering (Fix terminal flickering — raw ANSI escape codes bypass Ink render system #254) — related resource/rendering pressure

[github-actions]

📋 Assigned to Fenster (Core Dev)

Issue: #259 — Investigate: VS Code crash during Squad execution

Fenster will pick this up in the next Copilot session.

For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say:
Fenster, work on issue #259