Composer 2 is automatically applied

Support Bug Reports
, , ,
1

Describe the Bug

When running an agent with Opus 4.6, Cursor automatically spins up a subagent using Composer 2. That subagent then explores the project on its own.

The issue is that this happens multiple times, which makes the process very slow and blocks progress. In practice, Composer 2 appears to be handling work that Opus 4.6 was explicitly selected for, and it is not performing that work well enough to justify the automatic handoff.

Steps to Reproduce

Use Opus 4.6 and give it a moderately complex task on a small project.

Expected Behavior

The selected model should be the one that performs the task. If Cursor automatically delegates work to another model to save tokens or improve efficiency, that delegation should only happen when it clearly improves the outcome rather than making it slower or worse.

Operating System

Windows 10/11

Version Information

IDE: 3.0.13

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hi @Hans_Muster Thank you for reporting this. This is expected behavior but I have some tips that may be able to help improve your experience. One is that sometimes you can get prompted to approve an action on behalf of the subagent - sometimes that approval pops up to the main agent window (opus in this case) other times you may need to click into the subagent to allow list or approve the command. If you have notifications enabled, there is a small gap between the request for approval and the time the notification is sent. So it may appear that the agent is taking longer than you expect, when it is often waiting for approval / permission to continue working.

I’ll also mention that using more efficient models to take on modular subtasks is a standard across the industry and not something that Cursor does exclusively.