I was waiting a long time before realizing there was a sub-agent, I expected the main agent window to show if there was any approval needed on commands, but while checking why the sub-agent was stuck I discovered the sub-agent was blocked on approval of commands.
This is a waste of time if the main agent spawns different sub-agents I may not realize there’s no progress. Can this be fixed showing approvals in the main agent window?
I think this is a bad UX to hide a required user interaction inside the sub-agents dropdown to be expanded and clicking the sub-agent list item to open the sub-agent window and notice the (hidden) pending approval.
I mean in the IDE sidebar agent window, I didn’t try to see on the non-IDE agent window if the approvals of sub-agents are shown on the main agent chat too
Yeah the non-IDE agents window (which I almost never use) does show the sub-agent approval in the main agent window. So the issue is only in the IDE main agent window
Thanks @t-ricci-aux, confirmed. The Agents Window surfaces a blocked sub-agent in the parent (orange dot plus Allow), but the IDE chat panel only shows “1 subagent running” with no approval cue. That gap is IDE-panel specific and we’ve passed it on. Until it’s fixed, turn on Cursor Settings → General → System Notifications so approvals pop with Accept/Reject, or run sub-agent-heavy work in the Agents Window. “Always Run” on the card allowlists those commands so later sub-agents don’t stop.