Subagent is stuck immediately in Stopped state

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I start a new chat session in cursor. I tell it to do some task. Sometimes subagents are spun up by the main orchestrating agent, but they immediately go into a “Stopped” status. The main agent says “Waiting for subagent”. Sometimes the subagent eventually seems to startup, but other times it never does and the main agent is waiting forever until I interrupt it.

This is now happening for almost every subagent that gets created. It makes it impossible to get work done because lots of tasks are routed automatically to subagents by the main controlling agent.

Steps to Reproduce

  1. Create a new chat session in cursor IDE
  2. Ask it to use subagents to research some topic of interest.
  3. Observe that subagents are created, but their status is “Stopped”

Expected Behavior

The subagents immediately start executing and are not blocked or stopped.

Screenshots / Screen Recordings

Screenshot 2026-08-05 at 6.16.29 PM.png
Screenshot 2026-08-05 at 6.16.29 PM.png1672×624 33.4 KB

Operating System

MacOS

Version Information

Version: 3.14.7 (Universal)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
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: Darwin arm64 25.6.0

For AI issues: which model did you use?

GPT-5.6 Luna Medium. But it happens with ANY model.

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey Alan,

That “Stopped” label is, in most cases, just a display issue - the subagent is still running behind it even while the parent shows “Waiting for subagent.” Not something on your end, and it’s an issue we’re tracking.

In the meantime:

  • Don’t interrupt or re-prompt to “wake” it - it usually keeps working and finishes on its own, and interrupting can spawn a duplicate subagent and burn extra tokens.
  • If the parent looks stuck after a subagent has finished, click into that subagent’s card - that often nudges the completion through so the main agent moves on.
  • If it still never completes even after that, grab a request ID (three-dot menu → Copy Request ID, with Privacy Mode off) and drop it here so we can trace it: Reporting bugs / request IDs.

I’ll post back when there’s an update.