claude-code - 💡(How to fix) Fix Agent Teams: model parameter does not support version pinning [1 participants]

model: "opus" → resolves to latest (currently claude-opus-4-7) model: "claude-opus-4-6" → InputValidationError: Invalid option model: "claude-opus-4.6" → InputValidationError: Invalid option (omitted) → inherits user's /config default (workaround)

TL;DR

Update the model parameter validation to accept full model IDs in addition to family shorthand strings.

Guidance

• Review the enum validation for the model parameter to identify why it only accepts the three family shorthand strings ("sonnet", "opus", "haiku").
• Consider modifying the validation to allow full model IDs (e.g., claude-opus-4-6, claude-sonnet-4-6) as valid input.
• Test the updated validation with different model IDs to ensure it works as expected.
• Evaluate the impact of this change on existing workflows and configurations, particularly those relying on the global /config default.

Example

No code snippet is provided as the issue does not include specific implementation details.

Notes

The proposed solution assumes that updating the validation is feasible and does not introduce unintended consequences. Additional testing and review may be necessary to ensure compatibility with existing features and configurations.

Recommendation

Apply a workaround by omitting the model parameter to inherit the user's configured default model, but consider updating the validation to support full model IDs for more fine-grained control. This is because the current workaround only supports a single default model, which may not meet the requirements of all use cases.