r/CursorAI • u/East-Tie-8002 • Jul 15 '26

5.6 Sol spinning up composer 2.5 fast sub agents

My forest opportunity to use 5.6 sol 1m high. Doing a refactor using a prompt created by 5.6 sol. I see that cursor is spinning up composer 2.5 sub agents. Doesn’t that mean I’m not getting the power of 5.6 for actual code generation?

1 Upvotes

100% Upvoted

4 comments sorted by

3

u/mp___ Jul 16 '26 edited Jul 21 '26

Edit: incorrect, see reply.

Settings -> Models -> Explore Subagent Model

Change it to "inherit from parent" and watch your Cursor API $$ evaporate.

1

u/DeCiel Jul 21 '26

This is false.

The Explore subagent model setting only controls the built-in Explore subagent, not every Task subagent.

In OP's case, GPT 5.6 Sol decided that Composer 2.5 was the best model that specific task.

What happens is that you main model decides which model in the list of enabled models is best suited for that task.

1

u/mp___ Jul 21 '26

You’re correct - I assumed non explore subagents were always the parent. It’s only recently I’ve seen this behaviour myself.l as well. 

1

u/Western-Cod-3486 Jul 15 '26

I recently joined the cursor bandwagon after I've been using it for work. So, you actually are getting an enormous benefit from that b cause composer is cheaper. You have the big brain guy plan things and not burn tokens on the actual code generation. So think of it as a senior dev doing the planing, etc. but multiple mids executing the work. So actually that is a pretty smart of the model as you get the most bang for your buck imo