Subagents are getting stopped right after they start

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

subagents are getting stopped right after they start. sometime they work when i wake it after sending a message and undoing that message. but this is constantly a very big problem in my workflow. i have been paying 200$ per month for the last 8 months or so. please solve this bug. it been there for more than 20 days. grok 4.6 is also too slow even in fast mode and sometimes does not work aswell/high demand problem.

Steps to Reproduce

any long task where the subagents are started by the parent agent.

Expected Behavior

subagents work without stopping.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.17.8 (system setup)
VS Code Extension API: 1.128.0
Commit: 2fdd31c9f33f7fbe501f2d57772dc5bf64b63620
Date: 2026-08-20T02:18:12.724Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey @Siraj_Shaikh, thanks for the report and the screenshot.

First, you are on 3.17.8, and there have been a number of fixes to how subagents start, stop and report back since then. Please update to the latest version (v3.19 from https://cursor.com/download) and let us know if you still encounter issues!

I’ve updated and I continue to have this problem on 3.19.13 (system setup)