You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Support for Model Variants in (sub)agents #6645
---description: Performs security audits and identifies vulnerabilitiesmode: subagentmodel: anthropic/claude-sonnet-4-5:fasttools:
write: falseedit: false---
You are a security expert. Focus on identifying potential security issues.
Analyze the provided code and identify vulnerabilities such as SQL injection,
XSS, or insecure dependency versions.
when i use a config with variants an did not specify any it takes the default model but that seems to prefer thinking.
it errors with
{"message":"The model returned the following errors: messages.1.content.0.type: Expected `thinking` or `redacted_thinking`, but found `text`. When `thinking` is enabled, a final `assistant` message must start with a thinking block (preceeding the lastmost set of `tool_use` and `tool_result` blocks). We recommend you include thinking blocks from previous turns. To avoid this requirement, disable `thinking`. Please consult our documentation at https://docs.claude.com/en/docs/build-with-claude/extended-thinking"}. Received Model Group=anthropic/claude-4-5-sonnet
Available Model Group Fallbacks=Non
This issue might be a duplicate of existing issues. Please check:
claude sonnet "thinking"? #1106: Specifically asks about how to use Claude Sonnet with thinking mode, which is directly related to your feature request for model variants support
[FEATURE]: custom model aliases #3439: Feature request for custom model aliases, which could be an alternative approach to managing different model configurations
Feel free to ignore if none of these address your specific case.
@Blankf can you elaborate how the id field works to setup the variant? I'd also like to configure a model and a variant in my agent definition but couldn't figure out how to do that (without falling back to full model aliases).
This addresses the original request - you can now configure which variant each agent uses by default, without needing model aliases or the :variant suffix syntax.
The variant priority order is:
Explicit user selection (--variant or ctrl+t)
Agent's configured default variant
None (model's base behavior)
Reacted by Michael Jakl, Abhirup Das, Chindriș Mihai - Alexandru, Zach Mushac and Happydev
Reacted by Chindriș Mihai - Alexandru and Slothrup
Activity
github-actions commentedon Jan 2, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
Blankf commentedon Jan 2, 2026
it seems the id field is it, i missed that i guess.
mjakl commentedon Jan 5, 2026
@Blankf can you elaborate how the
idfield works to setup thevariant? I'd also like to configure a model and a variant in my agent definition but couldn't figure out how to do that (without falling back to full model aliases).CasualDeveloper commentedon Jan 7, 2026
For anyone following this issue - there's now an active effort to properly implement agent-level variant configuration:
Both PRs add a
variantfield to agent config:{ "agent": { "security-auditor": { "model": "anthropic/claude-sonnet-4-5", "variant": "fast" } } }This addresses the original request - you can now configure which variant each agent uses by default, without needing model aliases or the
:variantsuffix syntax.The variant priority order is:
--variantorctrl+t)