MiniMax-M3 context window value disputed across sources

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

• #43338 fix(model_metadata): MiniMax-M3 reports true 1M context, not 512K

  merged to main

  files: agent/model_metadata.py

  Show the diff

  • agent/model_metadata.py

    @@ -1838,6 +1838,17 @@ def get_model_context_length(
             from agent.models_dev import lookup_models_dev_context
             ctx = lookup_models_dev_context(effective_provider, model)
             if ctx:
    +            # MiniMax M3: models.dev reports 512K but actual context is 1M.
    +            # Prefer hardcoded catalog over stale probe value.
    +            if _model_name_suggests_minimax_m3(model):
    +                catalog = DEFAULT_CONTEXT_LENGTHS.get("minimax-m3")
    +                if catalog and ctx < catalog:
    +                    logger.info(
    +                        "Rejecting models.dev context=%s for %r "
    +                        "(MiniMax-M3 underreport); using hardcoded default %s",
    +                        ctx, model, f"{catalog:,}",
    +                    )
    +                    ctx = catalog
                 return ctx
     
         # 6. OpenRouter live API metadata — provider-unaware fallback.