Skip to content

Upgrade default MiniMax model to M3#94

Open
octo-patch wants to merge 1 commit into
FireRedTeam:mainfrom
octo-patch:feature/upgrade-minimax-m3
Open

Upgrade default MiniMax model to M3#94
octo-patch wants to merge 1 commit into
FireRedTeam:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch
Copy link
Copy Markdown

Summary

Bump the default model for the MiniMax recaption provider from MiniMax-M2.7 to MiniMax-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:

export RECAPTION_PROVIDER="minimax"
export OPENAI_COMPATIBLE_MODEL="MiniMax-M2.7"           # previous default
# or
export OPENAI_COMPATIBLE_MODEL="MiniMax-M2.7-highspeed" # previous highspeed variant

Changes

  • agent/llm_provider.pyOpenAICompatibleProvider's default model now MiniMax-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.pytest_defaults_to_minimax asserts the new default.
  • tests/test_integration.py — explicit model= arguments in the live API tests bumped to MiniMax-M3.

Unchanged

  • Base URL: still https://api.minimax.io/v1.
  • Env vars: MINIMAX_API_KEY / OPENAI_COMPATIBLE_API_KEY, OPENAI_COMPATIBLE_BASE_URL, OPENAI_COMPATIBLE_MODEL, RECAPTION_PROVIDER.
  • Temperature clamping (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.
  • ROI detection (multimodal) still uses Gemini directly.

Test plan

  • pytest tests/test_llm_provider.py -v — 33/33 pass locally.
  • Manual factory check: get_recaption_provider() with RECAPTION_PROVIDER=minimax returns an OpenAICompatibleProvider whose _model is MiniMax-M3 and _base_url is https://api.minimax.io/v1.
  • Live tests/test_integration.py (requires RUN_INTEGRATION_TESTS=1 + a valid MINIMAX_API_KEY) — not run in this PR; unit tests cover the wiring.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant