The model Sunnet 4.5 is not in my allow list, but the agent create new sub-agent use Sonnet 4.5 as the subagent.
Steps to Reproduce
I use GLM 5.2 high as the main agent model, and ask to do some task, but some how the model decided to create sub agent and the model is Sonnet 4.5. I can’t reproduce every time because it just happened once.
I created new session to ask the create new subagent out of the list and as expected – all failed. But I have no idea how this happen.
Toggling a model on/off doesn’t block that model, it just removes it from your personal selectable list so it won’t clutter the model picker. It’s a personal filter, not an access restriction.
Some built-in subagents are configured with their own default model rather than inheriting your main agent’s model. When the main agent decides to spin one of these up, it’ll use that subagent’s default model (like Sonnet 4.5 for the browser-use subagent).
For users on individual / team plans without access to a strict model block/allowlist (that’s an Enterprise feature), you can steer this with a rule. An explicit model choice generally overrides the subagent’s built-in default. For example:
When creating a subagent with the Task tool, always set its model to GLM 5.2. Never use Sonnet for subagents.
One caveat: this won’t work for every subagent. Some, like the browser-use subagent, depend on capabilities that aren’t available on all models, so forcing certain models there may just fail to start.
Thanks for your reply. But I still insist in that this feature should be apply in personal selectable list because if the model choose a very bad model with low effect, the consequence… You know what I mean. I really hate try once more.
