Improve: Update model selection to use aliases instead of specific versions #379
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates model selection UI and pricing logic to use Claude Code model aliases (
sonnet
,opus
) instead of hardcoded version numbers, following best practices from the Claude Code documentation.Changes
calculate_cost
function in usage.rs to recognize both model aliases ('opus', 'sonnet') and full model names ('claude-opus-4', 'claude-sonnet-4')test_calculate_cost_with_aliases
,test_calculate_cost_partial_tokens
)installation_type
field)Rationale
Claude Code recommends using model aliases which automatically map to the latest model versions, avoiding hardcoded version numbers that become outdated. This keeps the UI and cost calculations accurate as new model versions are released.
Testing
Backward Compatibility
Fully backward compatible. Existing agents using full model names (
claude-opus-4-20250514
,claude-sonnet-4-5-20250929
) will continue to work. The pricing calculation now supports both aliases and full names via OR logic.Commits
installation_type
field to ClaudeInstallation struct🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]