Since the launch of the selector for choosing the subagent model it never worked. When you set any model the subagent still uses Composer 1 or 2 instead of the model selected
Steps to Reproduce
In Explore Subagent Model selector choose any model or set as inherit from parent
Start a new chat and request anything
Hey, thanks for the detailed report. This is a known issue. Right now, for subagents the model you pick in Explore Subagent Model Selector isn’t actually applied, and they fall back to Composer. It’s reproducible and not just on your side.
We’re tracking it internally, but I can’t share an exact fix timeline yet. Once there’s an update, I’ll reply in this thread.
If you really need a specific model right now, Max Mode helps in some cases since the forced Composer fallback for subagents doesn’t apply there. It’s not a full workaround though, more of a temporary option. Let me know if this is blocking anything critical.
Hey @MarceloDiani, quick update. Over the last couple months we’ve made a few improvements on our side around model selection for subagents. You’re on 3.6.21, and the current stable version is much newer, so it’s worth rechecking on the latest build.
Quick check:
In Settings → Agents → Subagents, set the model you want for the Explore subagent, or set it to Inherit from parent.
Open a new chat and run a task that creates an Explore subagent.
Check which model the subagent actually runs on.
If it works correctly now, no need to reply and I’ll close the thread. If the subagent still switches to Composer, especially the Fast option under an expensive parent model, reply here with details and, if you can, the Request ID for the subagent request, and we’ll take another look.