Skip to content

feat: upgrade MiniMax default model to M3#2368

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

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

Conversation

@octo-patch
Copy link
Copy Markdown
Contributor

Summary

Upgrade MiniMax model configuration to include the latest M3 model as the new default for the minimax provider, while keeping the existing MiniMax-M2.7 and MiniMax-M2.7-highspeed options available.

Changes

  • Add MiniMax-M3 as the new flagship/default recommended model in the minimax provider entry of bot/vikingbot/providers/registry.py.
  • Update bot/README.md recommended models block to suggest MiniMax-M3 as the default while retaining M2.7 and M2.7-highspeed as alternatives.
  • Add unit tests covering MiniMax-M3 keyword matching, LiteLLM prefix resolution (minimax/MiniMax-M3), and system message merging behavior.

Why

MiniMax-M3 is the new flagship MiniMax model with broader capabilities than M2.7, and surfacing it as the recommended default lets users opt in to the latest model without manual research.

Testing

  • pytest bot/tests/test_minimax_provider.py — 20 tests pass (including new MiniMax-M3 cases).

Type of Change

  • New feature (feat)
  • Bug fix (fix)
  • Documentation (docs)
  • Refactoring (refactor)
  • Other

Checklist

  • Code follows project style guidelines (ruff clean)
  • Tests added for new functionality
  • Documentation updated (bot/README.md)
  • All tests pass

Add MiniMax-M3 as the new flagship/default recommended model alongside
the existing MiniMax-M2.7 and MiniMax-M2.7-highspeed options.

- Update provider registry comment to list M3 as default with M2.7 as alternative.
- Update bot README recommended models block to suggest M3.
- Add unit tests for M3 keyword match, prefix resolution, and system message merging.

Co-Authored-By: Octopus <liyuan851277048@icloud.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🏅 Score: 100
🧪 PR contains tests
🔒 No security concerns identified
✅ No TODO sections
🔀 No multiple PR themes
⚡ No major issues detected

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

PR Code Suggestions ✨

No code suggestions found for the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant