Cairn
NousResearch/hermes-agent

Provider prefix handling in model context length lookup

Cluster 47782 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and fixes address bugs where model context length lookups return inconsistent or incorrect results depending on whether the model ID includes a slash-separated provider prefix. Multiple fixes target prefix stripping and fuzzy matching logic in model metadata utilities.

Open issues1

  • Issue#47782[Bug]: get_model_context_length returns different context windows for the same model depending on whether the id is prefixed with provider/

Open PRs1

  • PR#95236fix(models): resolve slash-qualified ids through the parsed provider

3 PRs closed without merging

From the close comments: duplicate 1 · other 2

  • #47783 fix(model_metadata): strip slash-form provider prefix in _strip_provider_prefix · other
  • #47810 fix(model_metadata): parse slash-separated provider/model prefix in get_model_context_length · other
  • #47881 fix(agent): strip slash provider prefix in context length lookup (#47782) · duplicate → #47783, #47782, #47810
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.40: the share of item 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.

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 Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/47782.json
cluster/47782.md