Skip to content

[Feature] Add MiniMax-M3 model and set as default#1565

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

[Feature] Add MiniMax-M3 model and set as default#1565
octo-patch wants to merge 1 commit into
open-compass:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch

Copy link
Copy Markdown
Contributor

Summary

Update the MiniMax API integration to support the latest flagship model MiniMax-M3:

  • Add MiniMax-M3 to the api_models registry in vlmeval/config.py, placed before older versions so it surfaces first.
  • Switch the MiniMaxAPI default model argument from MiniMax-M2.7 to MiniMax-M3.
  • Drop the MiniMax-M2.5 and MiniMax-M2.5-highspeed registry entries to keep the supported list focused; MiniMax-M2.7 is kept as a legacy-compatible option.
  • Refresh the docstring in vlmeval/api/minimax_api.py so the documented model list matches the registry.

Notes

  • API base URL (https://api.minimax.io/v1/chat/completions), env vars, and unrelated providers (including the abab* GPT4V entries) are untouched.
  • Existing users of MiniMax-M2.7 are unaffected.

Test plan

  • python3 -m py_compile vlmeval/api/minimax_api.py vlmeval/config.py
  • Spot-check that MiniMax-M3 is now the default in MiniMaxAPI and registered in api_models.
  • Confirm MiniMax-M2.5 / MiniMax-M2.5-highspeed are removed; MiniMax-M2.7 is still present.

Update the MiniMax API integration to support the new flagship model:

- Add `MiniMax-M3` to the api_models registry, placed before older
  versions so it shows up first in listings.
- Switch the `MiniMaxAPI` default `model` to `MiniMax-M3`.
- Drop the older `MiniMax-M2.5` and `MiniMax-M2.5-highspeed` registry
  entries to keep the supported list focused; `MiniMax-M2.7` is kept as
  a legacy-compatible option.
- Refresh the docstring in `vlmeval/api/minimax_api.py` to reflect the
  current supported model list.

API base URL, env vars, and unrelated providers are untouched.
@kennymckormick kennymckormick added this pull request to the merge queue Jun 2, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Jun 2, 2026
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