Skip to content

feat: upgrade MiniMax default model to M3#39

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

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

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

Upgrade the MiniMax provider default model from M2.5 to the latest MiniMax-M3, in line with MiniMax's currently published flagship. Keep M2.7 and M2.7-highspeed available as legacy options for users that prefer the previous generation; remove M2.5 and M2.5-highspeed from the menus and catalog.

Changes

  • install.sh
    • Interactive setup menu now lists: MiniMax-M3 (推荐) / MiniMax-M2.7 / MiniMax-M2.7-highspeed / 自定义
    • ensure_minimax_provider_config catalog (both Node and Python branches) registers M3, M2.7, M2.7-highspeed instead of the old M2.5 pair
  • config-menu.sh
    • Same updates applied to config_minimax and ensure_minimax_provider_config
  • examples/config.example.yaml
    • Comment line listing MiniMax models updated to the new lineup

Why

MiniMax M3 是当前官方旗舰;继续把 M2.5 作为默认会让新用户拿到老一代效果,并在 OpenClaw 的 provider catalog 里残留过期 model id。M2.7 系列仍保留,做老用户的兼容退路。

Test

  • bash -n install.sh / bash -n config-menu.sh 通过
  • 单独跑 ensure_minimax_provider_config minimax MiniMax-M3 /tmp/out.json (Node 和 Python 两条路径均验证),输出 JSON 内 models.providers.minimax.models 三个 ID 齐全、agents.defaults.models["minimax/MiniMax-M3"].alias = "Minimax"
  • 菜单选项 1 → AI_MODEL=MiniMax-M3 正确,国际/国内 base URL 未变

Add MiniMax-M3 as the new default model and remove older M2.5 / M2.5-highspeed variants. Keep M2.7 and M2.7-highspeed as legacy fallbacks.

Affected files:
- install.sh: model menu (1->M3, 2->M2.7, 3->M2.7-highspeed) + ensure_minimax_provider_config catalog (both node and python3 branches)
- config-menu.sh: same updates in config_minimax menu and ensure_minimax_provider_config function
- examples/config.example.yaml: comment line listing supported MiniMax models
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