Skip to content

feat: upgrade MiniMax default model to M3 (keep M2.7)#91

Open
octo-patch wants to merge 3 commits into
humanlayer:mainfrom
octo-patch:feature/add-minimax-provider
Open

feat: upgrade MiniMax default model to M3 (keep M2.7)#91
octo-patch wants to merge 3 commits into
humanlayer:mainfrom
octo-patch:feature/add-minimax-provider

Conversation

@octo-patch

@octo-patch octo-patch commented Mar 17, 2026

Copy link
Copy Markdown

Summary

Upgrade the MiniMax BAML provider clients to use MiniMax-M3 as the default model.

  • MiniMax-M3 is the latest model: 512K context window, 128K max output, image input support
  • MiniMax-M2.7 and MiniMax-M2.7-highspeed are kept as alternatives for backward compatibility
  • Older models (M2.5 / M2.5-highspeed) are removed
  • All clients continue to use MINIMAX_API_KEY and https://api.minimax.io/v1

Changes (6 files)

  • packages/create-12-factor-agent/template/baml_src/clients.baml — Add MiniMaxM3 client (placed first as default), keep MiniMaxM27 / MiniMaxM27Highspeed, remove MiniMaxM25 / MiniMaxM25Highspeed, update OpenaiFallback to use MiniMaxM3
  • workshops/2025-05/final/baml_src/clients.baml — Same updates for the workshop template
  • packages/create-12-factor-agent/template/test/minimax-provider.test.ts — 23 unit tests validating M3/M2.7 client config + assertions that M2.5/M2.1/M2/M1 are removed
  • packages/create-12-factor-agent/template/test/minimax-integration.test.ts — Live API tests for M3, M2.7, M2.7-highspeed
  • packages/create-12-factor-agent/template/baml_src/agent.baml — Update test comment from M2.5 to M3
  • packages/create-12-factor-agent/template/README.md — Document M3 as default client, list M2.7 alternatives

Test plan

  • 23/23 unit tests pass (npx tsx test/minimax-provider.test.ts)
  • Existing OpenAI and Anthropic clients unaffected
  • M3 declared before M2.7 to signal default placement

Add MiniMax M2.5 and M2.5-highspeed as pre-configured LLM provider
clients using BAML's OpenAI-compatible provider with custom base_url.
MiniMax offers a 204K context window and an OpenAI-compatible API.

Changes:
- Add MiniMaxM25 and MiniMaxM25Highspeed client definitions in
  clients.baml (template and workshop final)
- Include MiniMax in round-robin (CustomFast) and fallback
  (OpenaiFallback) strategies
- Add BAML test cases for MiniMax provider
- Add unit tests (14 tests) validating BAML configuration
- Add integration tests (5 tests) verifying MiniMax API compatibility
- Update README with MiniMax setup instructions and env var
@CLAassistant

CLAassistant commented Mar 17, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ octo-patch
❌ PR Bot


PR Bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Add MiniMax-M2.7 and MiniMax-M2.7-highspeed as the latest recommended
models, replacing M2.5 as the default in round-robin and fallback
strategies. M2.5 clients remain available for backward compatibility.

- Add MiniMaxM27 and MiniMaxM27Highspeed BAML client definitions
- Update CustomFast round-robin and OpenaiFallback to use M2.7
- Add 9 unit tests and 5 integration tests for M2.7 models
- Update README with M2.7 client documentation
@octo-patch octo-patch changed the title feat: add MiniMax as LLM provider in BAML client configuration feat: add MiniMax M2.5 & M2.7 as BAML LLM provider clients Mar 18, 2026
- Add MiniMax-M3 to model list and set as default
- Keep MiniMax-M2.7 and MiniMax-M2.7-highspeed
- Remove older models (M2.5/M2.5-highspeed)
- Update related tests
@octo-patch octo-patch changed the title feat: add MiniMax M2.5 & M2.7 as BAML LLM provider clients feat: upgrade MiniMax default model to M3 (keep M2.7) 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.

2 participants