Not able to open subagent execution window on IDE

Support Bug Reports
,
1

We’re no longer able to open the subagent window or get any output from it (both conversation, thoughts, and response).

Meaning:

  1. Subagent is invoked.

  2. We cannot access its process:

    1. Editor window: subagent invoked, stuck on stuck on “Planning next moves”, nothing happens when clicking the arrows button.
    2. Agents window: subagent invoked, stuck on “Planning next moves”. Nothing happens when clicking “Open”:
      Screenshot 2026-04-14 at 11.29.09
      Screenshot 2026-04-14 at 11.29.09532×209 12.1 KB

  3. Work is performed eventually, and main agent receives responses.

  4. Nothing is showing on the Cursor output windows.

  5. Happens for subagents created manually and using the task.

  6. Happens with all models, also with “inherit”.

PSB my setup.

Your help is appreciated.

Setup:

Version: 3.1.10 (Universal)
VSCode Version: 1.105.1
Commit: dacbe9b31599a253763e4910eb6ab38704653320
Date: 2026-04-13T11:39:16.806Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hi @vaiden,

This is a known issue that our team is actively investigating. The subagent window click behavior broke in recent builds — the button renders but the click doesn’t navigate to the subagent’s conversation. Your observation that the work still completes in the background is consistent with what we’re seeing: it’s purely a UI issue, not a problem with the subagent execution itself.

A couple of things that might help in the meantime:

  1. Reload Window (Cmd+Shift+P → “Developer: Reload Window”) — some users have found this temporarily restores the click behavior for the current session

  2. If Reload Window doesn’t help, could you check the Developer Console (Help > Toggle Developer Tools → Console tab) for any red error messages when you click “Open”? That would help narrow down whether there’s a JavaScript error blocking the overlay

Also noting that you mentioned this happens in both the editor layout and the Agents window — that’s a useful data point for the fix.

You may also find this related thread helpful, which describes a similar pattern.

8

Thanks for the prompt reply.
No error presented in dev tools upon clicking (both in editor and agents windows).

I don’t think it’s related but I do see this error in the logs (even without clicking):

workbench.desktop.main.js:41096 [composer] No first token received within 2s

1. {arch: 'arm64', platform: 'darwin', channel: 'stable', client_version: '3.1.10', requestId: 'ff51ebdc-0631-4b2e-83fc-77922e008345', …}

  1. arch: "arm64"
  2. channel: "stable"
  3. chatService: "agent"
  4. client_version: "3.1.10"
  5. composerId: "941328c2-e0c0-4377-822c-cee0519d015e"
  6. platform: "darwin"
  7. requestId: "ff51ebdc-0631-4b2e-83fc-77922e008345"
  8. thresholdMs: 2000
  9. [[Prototype]]: Object
9

Hi,
it happens to me as well, on Windows

PSB my setup.

Version: 3.1.10 (user setup)
VSCode Version: 1.105.1
Commit: dacbe9b31599a253763e4910eb6ab38704653320
Date: 2026-04-13T11:39:16.806Z
Layout: editor
Build Type: Stable
Release Track: Default
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

Thanks on advance

1 Like
10

Thanks for checking the Developer Console, @vaiden. The fact that no errors appear on click is actually a useful signal — it rules out a surface-level JS exception and points toward one of the deeper UI state issues the team is already tracking.

Regarding the [composer] No first token received within 2s warning — you’re right, that’s separate from the click issue. It relates to initial streaming latency and shouldn’t affect the subagent window behavior.

@Israel_Kovas - thanks for confirming this affects Windows as well. The team is actively working on a fix — the cross-platform confirmation helps scope it.

No action needed from either of you at this point. This will be resolved in an upcoming update.

1 Like