Skip to content

feat: upgrade MiniMax default model to M3#167

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

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

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

Upgrade MiniMax model references to feature the latest M3 model as the suggested default.

Changes

  • Add MiniMax-M3 as the suggested default in README.md, README_zh.md, config/env.example, docker/README.md, and src/sirchmunk/api/settings.py
  • Retain MiniMax-M2.7 and MiniMax-M2.7-highspeed as available alternatives
  • Drop the deprecated MiniMax-M2.5 reference from the supported models list

Why

MiniMax-M3 is the new flagship model with a 512K context window, 128K max output, and image input support across both OpenAI-compatible and Anthropic-compatible interfaces. Updating the documentation examples helps users land on the latest model out of the box.

Testing

  • Docs/config-only change; no code logic or API URL is modified
  • Verified no remaining references to M2.5 / M2.1 / M2 / M1 in the repo

- Add MiniMax-M3 as the suggested default in README, README_zh,
  config/env.example, docker/README.md and src/sirchmunk/api/settings.py
- Keep MiniMax-M2.7 / MiniMax-M2.7-highspeed as alternatives
- Drop deprecated MiniMax-M2.5 from the supported models list

Co-Authored-By: Octopus <liyuan851277048@icloud.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates references and examples across the documentation (English and Chinese READMEs, Docker README), configuration templates (env.example), and settings code (settings.py) to feature the newer MiniMax-M3 model instead of or alongside the older MiniMax-M2.7 model. There are no review comments to evaluate, and I have no additional feedback to provide.

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