Skip to content

feat: upgrade MiniMax default model to M3#2143

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

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

Conversation

@octo-patch
Copy link
Copy Markdown
Contributor

Summary

Upgrade MiniMax model configuration to use M3 as the default model.

Changes

File Change
data.json Add MiniMax-M3 and set as default; keep MiniMax-M2.7 and MiniMax-M2.7-highspeed; remove MiniMax-M2.5, MiniMax-M2.5-highspeed, MiniMax-Text-01
CustomForm.tsx Fix default Api Host to https://api.minimax.io/v1 (was .com)
test_minimax_provider.py Update test assertions for M3 as default; fix broken relative paths after test/test/llm/ move

Why M3?

MiniMax-M3 is the latest generation model from MiniMax, offering:

  • 512K context window
  • Up to 128K max output
  • Image input support (OpenAI- and Anthropic-compatible APIs)

Older M2.5 / M2.5-highspeed / Text-01 are removed to keep the model dropdown focused on actively recommended models. MiniMax-M2.7 and MiniMax-M2.7-highspeed remain available as the previous generation.

All models use the same OpenAI-compatible API endpoint (https://api.minimax.io/v1).

Test plan

  • All 34 unit tests pass (python -m unittest test.llm.test_minimax_provider)
  • Frontend data.json validated: M3 first, M2.7/M2.7-highspeed retained, older models removed
  • CustomForm default Api Host points to api.minimax.io/v1
  • Integration test with MINIMAX_API_KEY (requires API credit)

- Add MiniMax-M3 to model list and set as default
- Keep MiniMax-M2.7 and MiniMax-M2.7-highspeed
- Remove older models (M2.5/M2.5-highspeed/Text-01)
- Update related tests
- Fix CustomForm default Api Host to api.minimax.io/v1
- Fix relative test paths broken after test/ -> test/llm/ move
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