VSCode crashes while squad is running

[diberry]

I don't know if this is a Copilot CLI issue or a Squad issue - how would figure this out?

I run Copilot CLI in the main editor window, then have the terminal for my own interactions with the repo. Squad is the agent running and I could see it running on a task. At somepoint, VSCode just closes. I assume its a crash but there is no popup window.

Running in VSCode nightly build.

[bradygaster]

Thanks for reporting this, @diberry. We appreciate the detailed context.

This sounds like it could be a VSCode or Copilot extension-side crash, but we want to make sure Squad isn't contributing. Could you share: VSCode crash logs, which Squad task was running, system resource usage at the time, and whether this reproduces on stable (vs nightly)?

We're also auditing our resource footprint for potential memory/process issues. We'll update here with any findings.

[diberry]

Next time I see it, yes, will report back. I've had others report back to me they've also experience this.

[bradygaster]

📋 Filed a tracking issue for investigation. We want to make sure Squad isn't contributing to this, @diberry — Fenster will audit our resource footprint (memory, file watchers, process spawning). The terminal flicker fix (#254) may also help reduce overall resource pressure. We'll update here with findings!

Linked issue: #259