Cursor Composer stuck on thinking

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Post:
Problem:
Composer Agent gets stuck in “Thinking…” indefinitely when using multiple agents + subagents. No error, no way to recover.

Steps to Reproduce

Impact:
I have to kill the chat, start a new agent, and manually feed it the previous conversation context. Wastes time and tokens.

Expected Behavior

Proposed fix:
Add a “Repair” button or /repair command. It should auto-spawn a new agent, transfer the full context + files + subagent state, and continue where it left off.

Where it occurs: Cursor → Composer → Agent mode, multi-agent setup

Operating System

Windows 10/11

Version Information

Composer 2 / 2.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Markus_Granlund

Can you share a Request ID of an affected conversation?

We did have a few issues with Composer 2.5 yesterday (see our statuspage), and those should be reoslved now.

Hi Colin,

Thanks for the quick reply! :+1:

The original issue seems to be fixed now — no more problems with that.

However, a new issue has appeared:
When using multitask mode with multiple sub-agents, the agent sometimes fails to generate the final summary from the sub-agents. In these cases, I can’t open the final output text (the “Open” button doesn’t work or the text stays stuck/unreadable).

Sometimes the text is visible, sometimes it’s not. Restarting Cursor usually fixes it and makes the text readable again.

The problem is intermittent but recurring.

Could you look into this as well?

Thanks!
Markus

Let’s stick to one topic per thread. :slight_smile: Feel free to raise a new one, with a fresh bug report. Please make sure to include your full Cursor version info.