Agent disconnected from the Subagent

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Agent assigned a job to the Subagent. At some point, the Subagent’s chat call item disappeared from the Agent’s chat, and the Agent said that it received an ENUM instead of a Subagent.

Steps to Reproduce

I don’t know. I closed the extra tabs, including the chat tab with the Subagent, and then reopened it. At that moment, I suddenly received a notification that the Agent had ended, even though the Subagent was still working (I was reading his chat).

Operating System

Windows 10/11

Version Information

Version: 2.7.0-pre.162.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: 92e85966ce9c672870440d2813862a59d72f61e0
Date: 2026-03-29T02:02:20.824Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

Main: Composer 2 Fast
Sub: GPT-5.1 Codex Max

For AI issues: add Request ID with privacy disabled

Main: dcfb7c6c-37c1-46e4-8de9-7699ae7871ac
Sub: f2a3a5c4-7460-40a4-9bd6-ff87e06cc858

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Hey, thanks for the report and the request IDs, super helpful.

This looks like a known issue on Nightly builds where the subagent UI disappears from the main agent chat. The team is aware and tracking it, but there’s no ETA yet. Your report, and especially the request IDs, helps us prioritize it.

A couple quick questions:

  1. Is this happening every time, or was it a one-off?
  2. When you closed and reopened the subagent tab, did the subagent chat still show its progress, or was it empty?

If this is blocking your workflow, switching to the Default release track for now could be a workaround since this seems more common on Nightly.

Let me know how it goes.

7
  1. First miting
  2. The subagent was thinking in his chat, and then he gave an answer to the task he was working on. If I had managed to reopen it, it’s possible that it disconnected from the Agent when I opened its chat. :thinking:
1 Like
8

This started happening regularly.

I encountered it again, rolled back to the stable update channel, and encountered it two times in a row again.

RID: a98756e6-be75-482d-8f7d-86dd1fa946d6

1 Like