feat(wizard): bump MiniMax default to M3#555
Open
octo-patch wants to merge 1 commit into
Open
Conversation
octo-patch
force-pushed
the
feature/upgrade-minimax-m3
branch
from
2236592 to
9e09a40
Compare
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
Update the wizard's MiniMax provider entry to use M3 as the new default model. M3 is the latest MiniMax flagship (512K context, 128K max output, image input supported across both OAI and Anthropic protocols). Keep
M2.7(andM2.7-highspeed) as alternates; drop the olderM2.5.Changes
assets/configure_mykey.py: switch theminimaxprovider name/description/default model fromMiniMax-M2.7toMiniMax-M3; refreshmodel_choicesto[M3, M2.7, M2.7-highspeed](M3 first/default, drop M2.5).mykey_template.py: align the two commented MiniMax snippets (Anthropic + OAI paths) — switch the examplemodeltoMiniMax-M3and update the supported-models / context-window notes to mention M3 (512K).Net diff: 11+/11- across two files; no behavioural changes outside the wizard's default value and the model_choices list.
Why
MiniMax-M3is the latest MiniMax flagship — 512K context, up to 128K output, image input on both OAI-compatible and Anthropic-compatible endpoints — so it should be the wizard's recommended default for new installs. KeepingM2.7andM2.7-highspeedinmodel_choicespreserves the option to fall back for users who want the previous generation.Testing
assets/configure_mykey.py: imports + the wizard's provider list lookup still works;LLM_PROVIDERS[minimax].template.model == 'MiniMax-M3'andmodel_choices == ['MiniMax-M3', 'MiniMax-M2.7', 'MiniMax-M2.7-highspeed'].mykey_template.py: file is comment-only configuration examples — manual review.