Why are we using composer 1.5 for the Subagent system, why can’t we pick what model to use our self?
sorry i did not phase it right i do mean the Subagent not the agents
1 Like
Subagents do NOT automatically inherit the model you selected for the parent agent. By default, they use a faster/cheaper model (Cursor’s Composer model).
This almost certainly already has a thread. Did you search before posting, OP?
Only when MAX mode is enabled will the subagent inherit the main agent’s model. Otherwise, it falls back to composer1.5.
There is also a known bug where subagents that spawn additional subagents (level 2) always fall back to composer1.5, even when MAX mode is enabled.
See the reported bug:
https://forum.cursor.com/t/nested-subagents-dont-inherit-model-in-max-mode/152680
Just want to clarify that this is true for users on legacy, request based pricing, but not for users who are on the newer usage (token)-based pricing.
Built-in subagents have their own model defined (Composer) that can’t currently be changed!
Now that composer 2 has dropped, it would be nice it would now default to composer 2 rather than composer 1.5.
1 Like
@ianmoone163 That will happen, but it will take a client release! Coming soon.
1 Like
For me it seems to be defaulting to Composer 2 Fast as of Cursor v2.6.21. I’d strongly prefer to be able to set it to Composer 2 instead, given that it supposedly performs as well at 50% of the cost.
as per Cursor Doc by default subagent inherits model from parent agent
https://cursor.com/docs/subagents#model-configuration
”Uses the same model as the parent agent. This is the default.”
why cursor is using compose 2.0 ? as default its not useful its bad
one can make their own agent harness exclusively for working cursor-agent cli agents