NousResearch/hermes-agent

Provider-aware context length resolution fixes

Cluster 37808 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These issues and PRs address bugs in context-length lookup logic, including passing provider and configuration details through the resolution chain and eliminating unnecessary OpenRouter metadata fetches on cold start.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #37837 fix(tools): pass base_url, provider, config_context_length to context-length lookup · done elsewhere → 03841c9, c454d32, #37808
  • #37901 fix(tools): pass active provider to context resolver · superseded by another PR → 03841c9, c454d32
Closed issues · 1
  • Closed#37808Bug: _resolve_active_context_length() triggers unnecessary OpenRouter metadata fetch on every cold start (~5-6s overhead)
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.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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.