Skip to content

feat: upgrade MiniMax default model to M3#1859

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

feat: upgrade MiniMax default model to M3#1859
octo-patch wants to merge 1 commit into
MemTensor:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch

@octo-patch octo-patch commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Upgrades the MiniMax default chat model from M2.7 to M3 in MemOS, following the established pattern from the merged PR #1291 (M2.6 -> M2.7).

M3 is the new MiniMax flagship: 512K context window, 128K max output tokens, and image input support across both the OpenAI-compatible and Anthropic-compatible interfaces exposed by https://api.minimax.io.

Changes

  • src/memos/api/config.py: Default MOS_CHAT_MODEL fallback switched from MiniMax-M2.7 to MiniMax-M3 in APIConfig.minimax_config().
  • examples/basic_modules/llm.py: Scenario 7 example updated to use MiniMax-M3, and the "Available models" comment refreshed to list the current supported set.

Model support matrix

Model Status
MiniMax-M3 New default (flagship)
MiniMax-M2.7 Retained (still supported)
MiniMax-M2.7-highspeed Retained (low-latency)
MiniMax-M2.5 Dropped from example list (deprecated upstream)
MiniMax-M2.5-highspeed Dropped from example list (deprecated upstream)

M2.7 and M2.7-highspeed are intentionally kept: the change only flips the default when MOS_CHAT_MODEL is unset; users who pin a specific model via env var are unaffected. The MinimaxLLM and MinimaxLLMConfig classes are untouched, and no API URL or provider wiring changes are introduced.

Scope

  • Pure config/default change.
  • No dependency bumps, no API URL changes, no new provider wiring.
  • Test pinning (tests/llms/test_minimax.py, tests/configs/test_llm.py) continues to exercise M2.7 / M2.7-highspeed and is unchanged.

Verification

  • python -m pytest tests/llms/test_minimax.py tests/configs/test_llm.py continues to pass (existing tests pin M2.7 / M2.7-highspeed, both still valid).
  • Confirmed MiniMax-M3 is reachable via the OpenAI-compatible endpoint at https://api.minimax.io/v1.

- Set MiniMax-M3 as the new default in the API config
- Update example to use MiniMax-M3 and refresh the available models list
- Retain MiniMax-M2.7 and MiniMax-M2.7-highspeed; drop the deprecated
  MiniMax-M2.5 and MiniMax-M2.5-highspeed entries from the example

MiniMax-M3 is the new flagship model with 512K context window, 128K max
output, and image input support across both OpenAI-compatible and
Anthropic-compatible interfaces.

Co-Authored-By: Octopus <liyuan851277048@icloud.com>
@octo-patch octo-patch force-pushed the feature/upgrade-minimax-m3 branch from f33c69b to b1ba305 Compare June 3, 2026 13:38
@Memtensor-AI Memtensor-AI changed the base branch from dev-20260604-v2.0.19 to dev-v2.0.22 July 1, 2026 13:16
@Memtensor-AI

Copy link
Copy Markdown
Collaborator

Automated Test Results: PASSED

Cloud test-engine rerun against dev-v2.0.22 completed successfully after migrating this run from the old 10010 queue to the updated cloud test-engine.

  • Run: tr-e2ca5fa4-4b5 on cloud test-engine 10011
  • Scope: memos_python_core/changed-python-source
  • Result: 2 passed, 0 failed, 0 skipped

Manual code review is still required before merge.

@CarltonXiang CarltonXiang deleted the branch MemTensor:main July 3, 2026 07:25
@syzsunshine219 syzsunshine219 reopened this Jul 3, 2026
@syzsunshine219 syzsunshine219 added the needs-audit Requires manual audit before merge label Jul 3, 2026
@syzsunshine219 syzsunshine219 changed the base branch from dev-v2.0.22 to main July 3, 2026 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-audit Requires manual audit before merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants