max_tokens misread as context length in local probe
Cluster 93412. Data as of
Nothing open on GitHub. Fix merged in #93652 on 24 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #93652. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93652. That is separate from the fix event. - Still open
- 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.
Open issues0
Open PRs0
Fixes on record
-
#93652 fix(model-metadata): 1M-context local endpoints no longer detected at their output cap (#93412, salvage #65574 + #71442 + #93423)
files:
agent/model_metadata.py,tests/agent/test_model_metadata_local_ctx.py
2 PRs closed without merging
From the close comments: duplicate 1 · merged via another change 1
Closed issues · 1
- Closed#93412[Bug]: Local context probe misreads max_tokens (output cap) as context length — 1M context endpoint detected as 393K
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #93652
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 24 Aug 2026