When a subagent defined in the Team Marketplace Plugin is invoked, it does not respect the model defined in the subagent, but rather is invoked with the main agent model.
Steps to Reproduce
Create a Plugin with a subagent.
Define a model in that subagent, i.e. ‘composer-2’.
Start a new chat, select a different model, i.e. ‘sonnet 4.6’
run a command that will invoke that agent
subagent will be invoked with sonnet 4.6 model
Expected Behavior
Subagent should use the model specified in the subagent definition
This is a known issue. The model field in the marketplace plugin subagents is not being honored — the subagent defaults to the parent agent’s model (or Composer, depending on your plan’s pricing model) regardless of what you configure.
This has been reported by several other users, and the team is aware. A fix was recently shipped for local subagents (defined in .cursor/agents/), but marketplace plugin subagents are still affected.
As a workaround, you can define the subagent locally in your .cursor/agents/ directory with the desired model instead of relying on the marketplace plugin definition. Local subagents do respect the model field. More details on setup here: Subagents - Model configuration