# NousResearch/hermes-agent · MiniMax-M3 context window value disputed across sources

## Open now

- Nothing open on GitHub.

These issues and PRs concern conflicting reports of MiniMax-M3's context window size, with different sources (live probes, models.dev, hardcoded catalog, and the TUI) variously reporting 512K or 1M. Members propose fixes in both directions, reflecting ongoing disagreement about the authoritative value.

## TL;DR

- 8 member(s): 0 open issue(s), 3 closed issue(s), 0 open PR(s), 1 merged PR(s), 4 PR(s) closed without merging.
- A fix was merged to main in PR #43338. Verify it addresses your case.
- **Recommended:** read PR #43338 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `partially_resolved` · deciding PR(s): `pr-43338`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.20`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #37289: MiniMax-M3 context window inconsistency: hardcoded 1M vs models.dev 512K vs TUI status bar 512K
- #42333: Stale-context guard: drop live-probe values for M3 in favor of hardcoded catalog
- #43400: minimax m3 supports a context of 1m, but hermes always automatically recognizes 512k

## Prior & competing PRs

- **#43338: fix(model_metadata): MiniMax-M3 reports true 1M context, not 512K**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - files: `agent/model_metadata.py`
  - fix hunks:
  - `agent/model_metadata.py`

    ```diff
    @@ -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.
    ```
- **#43464: \[verified\] fix minimax m3 context resolution**. closed without merge · fix tier `suggested`
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `5a4297a11a83c38ac24eec7df0e4e41d6b3dbb9f`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#37335: fix(models): correct MiniMax-M3 context window to 512K (was hardcoded 1M)**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`
- **#42342: fix(model_metadata): prefer catalog 1M over stale probe for MiniMax M3**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#43338`
- **#43469: fix(model): invalidate stale MiniMax-M3 cache entries up to 512K**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#43464`, `#43469`, `#43464`, `#43464`, `#43464`, `#43464`

## Fix status

- Merged to main in PR #43338 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-06-10`.
- Subsystem: `agent`