Skip to content

feat: upgrade MiniMax default model to M3#1979

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

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

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

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

Changes

  • Add MiniMax-M3 to the model selection list and set as default
  • Keep MiniMax-M2.7 and MiniMax-M2.7-highspeed as alternatives
  • Remove older models (M2.5/M2.1/M2/M1)
  • Update CLI default for --model flag (minimax/minimax-m3)
  • Update related unit tests (wiki-llm-client.test.ts, wiki-flags.test.ts)
  • Update i18n / locale strings (en + zh-CN, web + CLI)
  • Update eval configs: replace minimax-2.5.yaml (M1 2.5) with minimax-m3.yaml; rename minimax-m2.1.yaml to minimax-m2.7.yaml (model ID also updated to m2.7)

Why

MiniMax-M3 is the latest model, with a 512K context window, up to 128K output, and image input support.

Testing

  • Unit tests updated to reference minimax/minimax-m3
  • Default model resolution path and CLI help text verified by grep — no stale M2.5 / m2.5 references remain in code

- 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.1/M2/M1)
- Update related tests, locales, CLI defaults, and eval configs
@vercel

vercel Bot commented Jun 2, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the NexusCore Team on Vercel.

A member of the Team first needs to authorize it.

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