[BUG] MiniMax provider, model m2.7 (when use as custom value ) - bad context length (extremly small)

[Rexarrior]

Problem (one or two sentences)

I've minimax setup for m2.7

And Roo show, that there is extremly small context window size: 1

Looks like, it don't catch context window size from provider. Also, there is no way to setup it through provider interface.

So, i think, it should be fixed: setup context size value catching from provider (if possible) or allow to change it from interface
p.s.
Ready to contribute, but in something about of month

Context (who is affected and when)

Happens when try to setup minimax tokenplan and use m2.7 highspeed model

Reproduction steps

1. Setup as presented on screenshot
2. say 'hi' in chat window
3. look on the context window usage

Expected result

Context windows show 204000 (because got it from provider or because it has been setuped from provider page in settings)

Actual result

Context windows show 1

Variations tried (optional)

It is possible to setup this model as OpenaiCompatible, then works correct

App Version

Version: 3.51.1 (7c9722b)

API Provider (optional)

Not Applicable / Other

Model Used (optional)

MiniMax-M2.7-highspeed

Roo Code Task Links (optional)

https://app.roocode.com/share/1304580d-0988-43fc-8ca3-3fb7c5f8d447

Relevant logs or errors (optional)

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

There are two related problems when a custom MiniMax model ID (like "MiniMax-M2.7-highspeed") is entered that does not exist in the hardcoded minimaxModels map:

1. Backend (src/api/providers/minimax.ts - getModel()): When the custom model ID is not found in minimaxModels, the handler silently replaces both the model ID and the model info with the defaults. This means the custom model the user intended to use is never actually sent to the MiniMax API -- requests are made with the default model ID instead.

2. Frontend (webview-ui/src/components/ui/hooks/useSelectedModel.ts - minimax case): The lookup minimaxModels[id] returns undefined for unrecognized model IDs. This undefined info flows to TaskHeader.tsx where model?.contextWindow || 1 falls back to displaying 1.

Proposed Fix

Backend (src/api/providers/minimax.ts):

• When a custom model ID is provided but not found in minimaxModels, use the custom model ID for API calls (so the user's intended model is actually used) but fall back to the default model's info (contextWindow, maxTokens, pricing, etc.) as sensible defaults.
• Change getModel() from:

  const id = modelId && modelId in minimaxModels ? (modelId as MinimaxModelId) : minimaxDefaultModelId
  const info = minimaxModels[id]

  To:

  const id = modelId || minimaxDefaultModelId
  const info = minimaxModels[id as MinimaxModelId] ?? minimaxModels[minimaxDefaultModelId]

Frontend (webview-ui/src/components/ui/hooks/useSelectedModel.ts):

• Apply the same fallback logic so the UI reflects the correct default model info for unknown model IDs:

  case "minimax": {
   const id = apiConfiguration.apiModelId ?? defaultModelId
   const info = minimaxModels[id as keyof typeof minimaxModels] ?? minimaxModels[defaultModelId as keyof typeof minimaxModels]
   return { id, info }
  }

Tests: Update existing tests and add new cases for custom/unknown model IDs in both minimax.spec.ts and useSelectedModel.spec.ts.

This approach ensures that (a) the user's custom model ID is actually sent to the MiniMax API, (b) sensible defaults are used for context window and other parameters, and (c) the UI displays accurate context window info instead of 1.

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