Skip to content

feat: upgrade MiniMax default model to M3#74

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

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

Conversation

@octo-patch

Copy link
Copy Markdown

Summary

Upgrade the documented MiniMax model configuration to include the latest M3 model as the default.

Changes

  • Add MiniMax-M3 to the supported model list and set it as the new default.
  • Retain MiniMax-M2.7 as an available alternative.
  • Remove deprecated MiniMax-M2.5 from the listed models.
  • Update README example and the integration test calls to use MiniMax-M3.

Why

MiniMax-M3 is the new flagship MiniMax model with a 512K context window, 128K max output, and image input support across both the OpenAI-compatible and Anthropic-compatible interfaces. Pointing the docs/tests at M3 ensures new users start with the recommended model while keeping M2.7 around for anyone who still needs the prior generation.

Testing

  • Existing unit tests in tests/test_minimax_provider.py pass with the updated model strings (28 tests, 3 skipped because they require MINIMAX_API_KEY).
  • Verified the MiniMax-M3 endpoint accepts requests against https://api.minimax.io/v1/chat/completions (the auth handshake completes; only billing-related responses gate the live call).

- Add MiniMax-M3 to the supported model list and set it as the new default
- Retain MiniMax-M2.7 as available alternative
- Remove deprecated MiniMax-M2.5 from the listed models
- Update README example and integration tests to use MiniMax-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