# NousResearch/hermes-agent · Provider-aware context length resolution fixes

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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.67`: 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

- #37808: Bug: _resolve_active_context_length() triggers unnecessary OpenRouter metadata fetch on every cold start (~5-6s overhead)

## Prior & competing PRs

- **#37837: fix(tools): pass base_url, provider, config_context_length to context-length lookup**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `03841c965`, `c454d32fe`, `#37808`
- **#37901: fix(tools): pass active provider to context resolver**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `03841c965`, `c454d32fe`

## Fix status

- No merged fix on record.
- Subsystem: `agent`