Only during exploration, even though I have my subagent and explore agent model set to composer 2.5 (not fast), it always default to 2.5 fast. Seeing as the fast variant takes ~3x more usage than the normal variant, for us on the pro/pro+ plans it can make a big difference.
Steps to Reproduce
Set the explore agent in Settings → Agents → Explore subagent model to Composer 2.5, hover and click edit, disable Fast.
Ask for any task where exploration is required, and you will see the agent is running as Composer 2.5 Fast.
Expected Behavior
The agents should be spawned as Composer 2.5 without fast mode enabled.
Hey, thanks for the report and the clear steps. This is a known regression. The explore subagent set via the UI with Fast turned off still resolves to Composer 2.5 Fast. I can reproduce it, and we’re tracking it on our side, but I don’t have an ETA yet.
This is a bad one as it actually racks up a lot of extra costs for long-horizon tasks where subagents keep getting spawned. The only solution was to switch to a non-fast model in the settings
Thanks, confirmed. This is the same regression described above, and it still reproduces on 3.6.31. We’ve reported it internally and are tracking it, but there’s no exact ETA for a fix yet.
On costs, I get it. In long tasks where subagents keep spawning, the Fast variant can really add up. As a temporary workaround, you’ve already found a good path: pick a model that doesn’t switch to Fast. I’ll post an update in this thread as soon as we have one.
I am still experiencing this issue, and unfortunately, it is happening across multiple models. It would be incredibly helpful to have a setting to completely turn off fast mode. I prioritize saving my subscription usage over generation speed.
Hey, thanks for coming back with an update. The subagent switching to Fast despite your setting is not intended behavior, and it’s not caused by anything in your configuration. We’re tracking this issue, but I can’t share an exact ETA yet.
On the original Composer 2.5 via picker case, we already made some progress, but since you’re seeing this across multiple models, it looks like a broader issue we’re still tracking separately. To pin down your exact situation, could you please share:
which models are affected where you set non-Fast but it runs as Fast
your Cursor version Settings > About or from the version window
the Request ID from a run where the subagent switched to Fast in the chat: top-right menu > Copy Request ID. If Privacy Mode is enabled, the Request ID may be unavailable
Temporary workaround: in Settings > Agents, for the explore subagent, pick a model that doesn’t have a Fast toggle. Then the usage won’t jump to 3x.
About a separate toggle to fully disable Fast, that’s a fair request. I’ll pass it along as feedback. There are similar threads already, and you can upvote them here: