feat: upgrade MiniMax default model to M3#994
Open
octo-patch wants to merge 3 commits into
Open
Conversation
- Add MiniMax to baseAiConfig with API base URL and platform link - MiniMax models (M2.5, M2.5-highspeed) are available via OpenAI-compatible API - Add unit tests verifying config entry structure - Add integration tests for chat completion and streaming
- Update integration tests to use MiniMax-M2.7 as primary model - Add MiniMax-M2.7-highspeed test - Add backward compatibility test for M2.5 - Keep all previous models as alternatives
- Add MiniMax-M3 to the MiniMax provider models list as the default - Keep MiniMax-M2.7 and MiniMax-M2.7-highspeed as alternatives - Remove MiniMax-M2.5 backward compatibility test - Add unit test verifying M3 is first in the models list Co-Authored-By: Octopus <liyuan851277048@icloud.com>
octo-patch
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Upgrade the MiniMax provider integration to use MiniMax-M3 as the default model, while keeping MiniMax-M2.7 and MiniMax-M2.7-highspeed as alternatives and removing the older MiniMax-M2.5 model.
Changes
src/app/core/setting/config.tsx: Add amodelsarray to the MiniMax entry inbaseAiConfiglisting MiniMax-M3, MiniMax-M2.7, and MiniMax-M2.7-highspeed (M3 first → default)src/app/core/setting/config.spec.mjs: New unit test verifying the MiniMax block has amodelsfield, M3 is the first model (default), and older models (M2.5/M2.1/M2/M1) are removedsrc/lib/ai/minimax-integration.spec.mjs: Update integration tests to use M3 as the default, keep M2.7 and M2.7-highspeed coverage, drop the M2.5 backward-compatibility testWhy
MiniMax-M3 is the latest generation: 512K context, up to 128K output, and image input support. It supersedes M2.5/M2.1/M2/M1, while M2.7 and M2.7-highspeed remain available for users who need them.
How It Works
Users selecting "MiniMax" from the provider creation dialog now get a pre-populated model list with MiniMax-M3 selected as the default. They can switch to M2.7 or M2.7-highspeed in the model selector if needed.
API Documentation