Cursor Multitask spawn agent model that not on the list

Support Help
,
1

Hi team,

Im using cursor multitask feature and realize that it spawn a model that not on my selected list. Because im a legacy user so if cursor accidentally spawn, for example. opus 4.7 which require max mode, then all my included request will be gone. Is this a bug? Thanks for helping.

Untitled
Untitled1152×822 22.2 KB

4

Hey, thanks for the request. This isn’t a bug, it’s expected behavior, and it’s safe for your included usage.

When a multitask agent delegates a subtask like explore or search to a built-in subagent, that subagent uses the Composer 2 family by default, usually composer-2-fast, for speed and cost. This happens no matter which model you picked in the main chat. That’s why you see Composer 2 Fast next to your main composer-2 in the screenshot. It won’t switch to Opus 4.7 or any other Max-only model. The default subagent is hardcoded to the Composer family, not to any model from the picker. Max-required models can only be used in a subagent if you turned on Max Mode for the main model.

Good news: in 3.3, currently in nightly, there’s now a selector for the subagent model. In Settings you’ll see a Subagents section with an Explore subagent model dropdown, so you can pick the model explicitly. To try it now, switch to nightly: Settings → Beta → Update Channel: Nightly.

On stable, you’ve got two options:

  • Turn on Max Mode for your selected model, then the subagent inherits the parent model.
  • Create a custom subagent in .cursor/agents/<name>.md and set the model in the frontmatter:
    ---
model: composer-2
---
    Then call it explicitly, like Use to …

More context and discussion here: How can I prevent Cursor from using composer - 2 - fast to create sub - agents? - #15 by deanrie