Skip to content

feat: upgrade MiniMax default model to M3 - #93

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

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

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

Upgrade the project's bundled MiniMax model entries to include the latest M3 flagship as the recommended option, while keeping M2.7 around for compatibility. Removes the deprecated M2.5 entry from the qingchenyun (qtcool) provider catalog.

Changes

  • translations/providers/files/extensions/qingchenyun/provider-catalog.ts
    • Add MiniMax-M3 (contextWindow: 524288, maxTokens: 131072) right after auto
    • Remove deprecated MiniMax-M2.5
    • Retain MiniMax-M2.7 as a fallback option
  • translations/panel/feature-panel.js
    • Add MiniMax-M3 to the built-in recommended models list (before M2.7) so it shows up in the Dashboard model picker
  • docs/INSTALL_GUIDE.md
    • Update the MiniMax quick-config example from minimax/MiniMax-M2.1 to minimax/MiniMax-M3
  • docs/guides/models-cn.md
    • Refresh the MiniMax version-selection table to list M3 (new default) and the M2.7 family
  • docs/upstream/wizard.md
    • Update the wizard provider summary row from M2.5 系列 to M3 / M2.7 系列

Why

MiniMax M3 is the new flagship model with a 512K context window and 128K max output. Surfacing it in the qingchenyun (qtcool) catalog and the recommended built-ins list lets users pick it directly from the Dashboard, and updating the docs keeps the quick-start examples pointing at a current, supported model name (the old MiniMax-M2.1 reference in INSTALL_GUIDE has been deprecated for a while).

The change is intentionally minimal: only the qingchenyun provider catalog and the panel built-ins list (project-owned code) are touched. Translation overlay rules in translations/extensions/*.json keep their existing left-hand match strings unchanged, since those have to keep matching the upstream OpenClaw source.

Testing

  • node cli/index.mjs status — translations config still loads (158 files, all categories detected)
  • All translations/**/*.json re-validated with json.load (no parse errors)
  • provider-catalog.ts and feature-panel.js syntax checked
  • Existing PR-check workflow (.github/workflows/pr-check.yml) covers JSON / shell / python validation

- Add MiniMax-M3 to qingchenyun provider catalog (512K context, 128K output)
- Add MiniMax-M3 to feature panel built-in models list (placed before M2.7)
- Retain MiniMax-M2.7 as the previous-generation option for compatibility
- Remove deprecated MiniMax-M2.5 from the catalog
- Update INSTALL_GUIDE / models-cn / wizard docs to reference M3
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