Minimax m2.5

[love8ko]

Problem (one or two sentences)

MiniMax has recently released the M2.5 model, which offers significant improvements over the previous version. The model is already available through the MiniMax API, but Roo Code’s model list hasn’t been updated to include it.

Context (who is affected and when)

Hi Roo Code team,

Thank you for the great extension — I use it daily and really appreciate your work!

I’m currently using MiniMax as my API provider (Roo Code v3.47.3). However, I noticed that the new MiniMax M2.5 model is not yet available in the model selection dropdown.

MiniMax has recently released the M2.5 model, which offers significant improvements over the previous version. The model is already available through the MiniMax API, but Roo Code’s model list hasn’t been updated to include it.

Current behavior:

MiniMax is available as a provider ✅
Only older MiniMax models appear in the model selector
M2.5 is not listed as an option
Expected behavior:

MiniMax-M2.5 (or the correct model ID) should appear in the MiniMax model dropdown
My setup:

Roo Code version: v3.47.3
Provider: MiniMax (using MiniMax API key directly)
Questions:

Are there any plans to add MiniMax M2.5 to the supported models list?
Is there an estimated timeline for this update?
As a workaround, is it possible to manually enter the model ID somewhere in the configuration?
Thank you in advance for your response!

Reproduction steps

update

Expected result

update

Actual result

update

Variations tried (optional)

No response

App Version

v3.47.3

API Provider (optional)

None

Model Used (optional)

minimax subscription

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed the codebase and here's my proposed implementation plan to add the MiniMax M2.5 model:

Changes needed:

1. packages/types/src/providers/minimax.ts - Add a "MiniMax-M2.5" entry to the minimaxModels object, following the same pattern as the existing M2, M2-Stable, and M2.1 entries. Also update minimaxDefaultModelId to "MiniMax-M2.5" since it's the latest model.
2. src/api/providers/__tests__/minimax.spec.ts - Add test coverage for the new M2.5 model configuration, and update the default model assertion to expect "MiniMax-M2.5".

The handler code in src/api/providers/minimax.ts is model-agnostic (it reads capabilities from the model definition), so no changes should be needed there.

Questions about model specs:

Before proceeding, I want to confirm a few details. Based on the existing M2/M2.1 entries, I'd assume the following defaults unless corrected:

• Model ID: MiniMax-M2.5 (matching the MiniMax-M{version} naming pattern)
• Context window: 192,000 tokens (same as M2/M2.1)
• Max output tokens: 16,384
• Pricing: $0.30 / $1.20 per million input/output tokens (same as M2/M2.1), cache writes $0.375, cache reads $0.03
• Supports prompt caching: Yes
• Supports images: No
• Preserve reasoning (thinking): Yes

If any of these specs differ for M2.5, please let me know and I'll adjust accordingly.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[love8ko]

@roomote Approved! Please proceed with the implementation.

The specs look correct to me. 👍

[roomote]

Thanks for the approval! I'll proceed with the implementation now. Will open a PR shortly with the MiniMax M2.5 model addition.

[roomote]

Implementation is up in PR #11458 (#11458). Added MiniMax-M2.5 to the models list and set it as the new default. All tests and lint checks pass. Feedback welcome!