Upgrade default MiniMax model to M3#94
Open
octo-patch wants to merge 1 commit into
Open
Conversation
The MiniMax recaption provider now defaults to `MiniMax-M3`, the latest generation in the MiniMax family. The previous default `MiniMax-M2.7` (and `MiniMax-M2.7-highspeed`) remain selectable via the `OPENAI_COMPATIBLE_MODEL` environment variable for backward compatibility. Changes: - agent/llm_provider.py: default model `MiniMax-M2.7` -> `MiniMax-M3` - agent/config.py: docstring updated to reflect new default - README.md: Option 2 (MiniMax) now mentions M3 as default; M2.7 / M2.7-highspeed listed as previous-generation alternatives - tests: assertions and integration-test model strings updated to M3 Base URL (`https://api.minimax.io/v1`), API-key env var (`MINIMAX_API_KEY` / `OPENAI_COMPATIBLE_API_KEY`) and the temperature clamping behaviour are unchanged. The ROI detection step still uses Gemini directly and is unaffected.
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.
Summary
Bump the default model for the
MiniMaxrecaption provider fromMiniMax-M2.7toMiniMax-M3, the latest generation released by MiniMax. M3 ships notable improvements over M2.7 (long-context understanding and instruction following), so it's a better fit for the recaption step that rewrites editing instructions.The previous default and its highspeed variant remain selectable for users who want to pin the older generation:
Changes
agent/llm_provider.py—OpenAICompatibleProvider's default model nowMiniMax-M3; docstrings updated.agent/config.py— comment block reflects new default.README.md— Option 2 (MiniMax) describes M3 as default; M2.7 and M2.7-highspeed listed as previous-generation alternatives.tests/test_llm_provider.py—test_defaults_to_minimaxasserts the new default.tests/test_integration.py— explicitmodel=arguments in the live API tests bumped toMiniMax-M3.Unchanged
https://api.minimax.io/v1.MINIMAX_API_KEY/OPENAI_COMPATIBLE_API_KEY,OPENAI_COMPATIBLE_BASE_URL,OPENAI_COMPATIBLE_MODEL,RECAPTION_PROVIDER.(0.01, 1.0]— required by MiniMax, applies to M3 the same way.<think>...</think>tag stripping — M3 still emits these in some configurations, so the existing post-processing is kept.Test plan
pytest tests/test_llm_provider.py -v— 33/33 pass locally.get_recaption_provider()withRECAPTION_PROVIDER=minimaxreturns anOpenAICompatibleProviderwhose_modelisMiniMax-M3and_base_urlishttps://api.minimax.io/v1.tests/test_integration.py(requiresRUN_INTEGRATION_TESTS=1+ a validMINIMAX_API_KEY) — not run in this PR; unit tests cover the wiring.