A similar problem, due to additional errors, the session crashes. It is the responses from the API that becomes empty. And for some reason, the subscription jumps either pro or ultra.
Hey, thanks for the report. Crashes with lots of parallel agents in multitask are a known class of client-side issues (the renderer under load), and we’re aware of it. I can’t share a specific fix timeline yet.
To understand which exact case you’re hitting, could you share a couple details:
The crash code or exit code, if shown (for example “code 133”, “code 5”)
What the crash looks like, does Cursor show a dialog, or does the window reload or close by itself
How much RAM your machine has
Does it happen with 1 to 2 agents, or only with 3+
For now, as a workaround, try running fewer agents in parallel. That reduces renderer load. Share the details above and I can dig deeper.
the app resets and pauses all works. the client seemingly clears, refreshes and then I’m shown my chat/IDE but nothing is in flight. all processes halted.
Thanks for the details, that helps clarify things. What you’re describing, the window resets, refreshes, and after that the IDE is open but all processes are stopped, is a renderer crash with an auto reload. There’s no crash code, but the behavior is pretty clear.
One important note about 48 GB. Free system memory won’t necessarily prevent this. The renderer process itself is crashing, and it has its own memory and CPU limits, independent of total RAM. When you run 3 or more agents in multitask, the load inside that process can spike quickly and it can crash. This isn’t about system memory.
This is a known class of issues with a high number of parallel agents, and we’re tracking it. I can’t share an ETA for a fix yet, but this is not intended behavior.
To make things more stable right now:
Keep it to 1 or 2 agents instead of 3 or more, since that seems to be around your threshold. You can try to find the exact point where it starts crashing
Disable unused extensions and MCP servers, each one adds load to the process
Right before it crashes, open Process Explorer via Cmd+Shift+P > Developer: Open Process Explorer to see what’s using the most resources
If you can catch a crash log or notice a specific trigger, like it only crashes after a certain action, send it here and I’ll add it to what we’re already tracking.
