Subagent will not open if you try to open it too early

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If you try to open a Subagent’s chat after it has appeared but before it has started working, the chat may be empty and the statuses may not update until the Subagent finishes working.

Steps to Reproduce

  1. Ask the Agent to launch the Subagent. You’ll likely need to pass a long prompt to the Subagent.
  2. Try clicking the Subagent’s call element before its status changes for the first time.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.12.6 (system setup)
VS Code Extension API: 1.128.0
Commit: 68ebb3d8033bceeb85416f924ff4bf5ea1220a20
Date: 2026-07-15T19:55:51.646Z
Layout: IDE
Build Type: Stable
Release Track: Nightly
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.256
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

any :thinking:

For AI issues: add Request ID with privacy disabled

agent: 11025594-6625-496d-944a-77e9629e6c46
subagent: e705d0fa-76b7-498f-9ec6-11b72e09eafe

Does this stop you from using Cursor

No - Cursor works, but with this issue

It seems like the screenshots show some other bug during a long session with many subagents, but the one described in the text also exists :upside_down_face:

Hey @Artemonim!

Thanks for the report. This was reported over here and a bug report was raised: Subagent Missing

I’ve attached this thread to that same report.

What I described in text is exactly the same bug.

But what I showed in the screenshots is something new that’s appeared in Nightly in the last 2-3 days. Subagent statuses in Agent chat are broken, and the Subagent chat doesn’t open until they complete the task, making monitoring Subagents impossible.


Or maybe this bug just showed up for me today and decided to stick around. :thinking:


Subagents’s end-of-work time is also broken, and it starts counting from the moment the chat with them is opened.

For want of a better word, I’m not sure I’m grokking the other bug. Could you raise a new bug report?

I discovered something funny: you can ask Agent-2 to find the transcript of a running Subagent, and it will give you a link to open the Subagent that won’t open from the chat with the Agent-Parent :clown_face:

Agent2-RID: 64d53674-b462-4255-99e7-9a4d019e9cac

Parrent-RID: 1a052434-b327-49cc-b712-7b71c777284d
Subagent-RID: f2f55966-3bb5-4e08-9a3f-981c713ac94a