Nous provider model metadata and context length handling
Cluster 24000 · agent. Data as of
Nothing open on GitHub. Fix merged in #24502 on 12 May 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #24502. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The three members relate to how model metadata, especially context length, is determined for the Nous provider. They cover using the Nous portal as a metadata source, a reported 32,768-token fallback affecting startup, and a change touching a Kimi 32k guard for Nous OpenRouter suffix matching.
Open issues0
Open PRs0
Fixes on record
-
#24502 Use nous portal as model metadata authority
files:
agent/model_metadata.py,tests/agent/test_model_metadata.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#24066 fix(model-metadata): extend Kimi 32k guard to Nous OpenRouter suffix-match · superseded by another PR →
528bba6,#24502
Closed issues · 1
- Closed#24000provider: nous falls back to 32,768-token context, blocking boot with model.context_length workaround required
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.67: 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
- Subsystem
- agent
- Merged PRs
- #24502
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 12 May 2026