Sub-agents stuck in "Loading Chat" mode, but still run on the main agent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi team — quick update from my side.

I updated Cursor and the original “Starting up” issue looks improved: subagents no longer get stuck there. They now show as Completed, and I also see an Allow button for subagent internal run command options.

However, I still have a blocker: when I click the subagent tile, it opens “Loading Chat” and stays stuck forever, so I can’t access the subagent chat at all.

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
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 24.6.0
Request ID: eff0ad7c-f5fe-4565-aa7d-f318268b7ed5

Steps to Reproduce

start a sub-agent

Expected Behavior

See the sub-agent chat

Operating System

MacOS

Version Information

Version: 3.2.11
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
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 24.6.0
Request ID: eff0ad7c-f5fe-4565-aa7d-f318268b7ed5

Additional Information

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @Dot_Hub,

Good news: the “Starting up” issue is resolved in v3.2.11. The “Loading Chat” stuck state you’re now seeing is a remaining edge case the team is actively working through.

To help narrow this down, could you share two things Dean mentioned in the original thread:

  1. A screenshot of the stuck “Loading Chat” state

  2. main.log snippets — open Cmd+Shift+P → Developer: Open Logs Folder, then look for entries containing [composer] or loadFromStorage around the time the subagent was started

In the meantime, try Reload Window (Cmd+Shift+P → “Developer: Reload Window”) — this has temporarily unstuck the subagent UI for some users.

You may also find this related thread helpful, where the same UI issue is being tracked.

couldn’t find it in the logs.

Thanks for the screenshots, these confirm the exact pattern the team is working on.

The fact that the subagent completes successfully (as shown in your second screenshot) while the tab stays stuck on “Loading Chat” matches what we’re seeing across reports. Not finding the log entries is also useful data — it suggests the composer data loading may be failing silently without logging an error, which helps narrow the root cause.

This is actively being investigated. Did the Reload Window workaround (Cmd+Shift+P → “Developer: Reload Window”) help temporarily, or does it stay stuck even after reloading?

Still stuck no matter what I do, I have also updated the Cursor version:
Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
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 24.6.0

Thanks for confirming. The fact that it persists on 3.2.16 (and that Reload Window doesn’t help) is useful data. This matches what we’re seeing from other reports of the same issue.

This is a known issue our team is investigating. I’ll follow up here once a fix is available.

v3.2.11 I still have this issue.

Now on Version: 3.2.21 (Universal) and the subagent window still does not load, which is a bummer because I rely on many skills etc that need them. Switched to claude code now in my daily work. Any timeline when this will be fixed?

Hey @Dot_Hub,
The subagent “Loading Chat” stuck state has been addressed in a recent Cursor update. Updating to the latest version should resolve this. Let me know if you’re still running into it!

cc @195440 @L_H