Repository navigation
feat(models): prefer MiniMax M3.1 Flash in supplier picker - #1402
Merged
Merged
Conversation
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
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.
Reason: SQLBot's built-in MiniMax picker still offers M3 and M2.7. Offer MiniMax-M3.1-Flash first and MiniMax-M3 second for new model selection.
Changes
Validation
git diff --checkpassed.BaseChatOpenAIand the productionOpenAILLM/LLMConfigclasses extracted without database imports, with real LangChain/OpenAI SDKs andhttpx.MockTransport. Sixteen model/endpoint/stream combinations passed, covering Flash, M3, saved M2.7 and custom IDs, both configured endpoint variants, image and tool history, streamed reasoning, and explicit Flash reasoning effort. This checks serialization only, not regional service availability.Limitations
The frontend build, full backend environment, database startup, browser flow, and live inference were not run. Frontend dependencies are absent, and heavy setup/builds are paused by the workspace resource gate (approximately 17 GiB free disk, below its 110 GiB threshold). No paid inference or real provider credentials were used.