feat: add MiniMax M2.5 model and set as default #11458
Draft
+20
−5
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.
Related GitHub Issue
Closes: #11457
Description
This PR attempts to address Issue #11457 by adding the MiniMax M2.5 model to the provider and making it the new default.
Changes:
MiniMax-M2.5entry tominimaxModelsinpackages/types/src/providers/minimax.tswith specs from the issue:minimaxDefaultModelIdfromMiniMax-M2toMiniMax-M2.5MINIMAX_DEFAULT_MAX_TOKENSto 131,072 to match the new default modelminimax.spec.tsThe existing M2, M2-Stable, and M2.1 models remain available for users who prefer them.
Feedback and guidance are welcome.
Test Procedure
cd src && npx vitest run api/providers/__tests__/minimax.spec.tsPre-Submission Checklist
Documentation Updates
Additional Notes
Model specs were provided by @ataniii in the issue comments. The M2.5 model uses the same API endpoint (
api.minimax.io) and Anthropic-compatible SDK path, so no handler changes were needed.