# NousResearch/hermes-agent · max_tokens misread as context length in local probe

## Open now

- Nothing open on GitHub.

A bug caused local model probing to incorrectly use max_tokens (an output cap) as the context length, leading to wrong context size detection (e.g., 1M-context endpoints reported as ~393K). Multiple fixes and related issues address this misreading.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #93652. Verify it addresses your case.
- **Recommended:** read PR #93652 (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: `resolved` · deciding PR(s): `pr-93652`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: 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

- #93412: \[Bug\]: Local context probe misreads max_tokens (output cap) as context length — 1M context endpoint detected as 393K

## Prior & competing PRs

- **#93652: fix(model-metadata): 1M-context local endpoints no longer detected at their output cap (#93412, salvage #65574 + #71442 + #93423)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `agent/model_metadata.py`, `tests/agent/test_model_metadata_local_ctx.py`
- **#93423: fix(model_metadata): stop misreading max_tokens as context length in local probe**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#93652`, `#65574`, `#71442`
- **#93473: fix(agent): stop treating max_tokens as context-length candidate (#93412)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#93423`

## Fix status

- Merged to main in PR #93652 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-24`.