Skip to content

feat: upgrade MiniMax default model to M3#1261

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

feat: upgrade MiniMax default model to M3#1261
octo-patch wants to merge 1 commit into
Marker-Inc-Korea:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch

Copy link
Copy Markdown
Contributor

Summary

Upgrade the minimax_llm generator module to use MiniMax-M3 as the new default model.

Changes

  • Add MiniMax-M3 (524,288 token context) to MAX_TOKEN_DICT, set as the new default
  • Retain MiniMax-M2.7 and MiniMax-M2.7-highspeed as available alternatives
  • Remove deprecated MiniMax-M2.5 / MiniMax-M2.5-highspeed entries
  • Update simple_minimax.yaml sample config to use M3
  • Update minimax_llm.md docs to reflect the new model list
  • Update unit tests to cover M3, M2.7, and M2.7-highspeed paths and assert legacy models are removed

Why

MiniMax-M3 is MiniMax's new flagship model with a 512K context window and 128K max output, and it is the recommended default for new integrations. M2.7 (and the high-speed variant) are kept available so users with existing configs continue to work.

Testing

  • pytest tests/autorag/nodes/generator/test_minimax.py passes (35 unit tests, 3 integration tests skipped without MINIMAX_API_KEY)
  • ruff check and ruff format clean

- Add MiniMax-M3 (524k context) to the supported model list, set as default
- Retain MiniMax-M2.7 and MiniMax-M2.7-highspeed for compatibility
- Remove deprecated MiniMax-M2.5 and MiniMax-M2.5-highspeed entries
- Update sample config, docs, and tests to reflect the new default
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