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

Support Bug Reports
,
1

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

2 Likes
6

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.