Hey there! This is a known limitation we’re actively working on. Running several agents in parallel inside one window can push that window past its memory budget and take the whole window down, which is why you get the “something happened unexpectedly” dialog rather than a single failed chat.
The key detail: each Cursor window runs as one process with a shared memory budget, and every agent, worktree, and loop in that window shares it. Stacking multiple agents into a single window concentrates all of it into that one process until the system kills it.
What helps in the meantime:
Spread agents across separate windows instead of stacking them in one. Each window gets its own memory budget, so no single process carries everything. Since you already run multiple windows, move the heavy agents into their own.
Run fewer agents in parallel per window.
Keep your Git change set small. Build output and dependencies (node_modules, dist, .next, etc.) showing up as thousands of changed or untracked files get streamed into that same process and inflate memory. Add them to your .gitignore and commit or stash work in progress.
Stay on the latest version, since we’ve been shipping improvements in this area.
To pin down exactly which crash you’re hitting, could you share:
The crash or exit code shown in the popup (for example “code 5” or “code 133”)
Your machine’s RAM
Roughly how many agents were running in parallel
If it keeps crashing, open Process Explorer (Ctrl+Shift+P then “Developer: Open Process Explorer”) and watch the memory climb right before a crash. A screenshot of that helps a lot. More on capturing diagnostics: Reporting bugs.
i dont recall seeing an exit code. i have 64gb of ram. i had many windows open and multiple agents running at the same time in a single window. if you see my previous issue, before when i was running 10 agents it wasnt crashing and i was playing whack-a-mole manually resuming them instead of them running to completion automatically