Cairn
NousResearch/hermes-agent

Reverse alias lookup returns wrong provider fix

Cluster 14614 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 PRs address a bug where reverse alias lookup in model resolution returns the incorrect provider when multiple providers share the same model. The fixes add guards and preference logic to ensure the correct provider is selected during alias resolution.

Open issues1

  • Issue#14614resolve_alias() reverse lookup returns wrong provider when multiple providers share the same model

Open PRs1

  • PR#14851fix(model-switch): prefer matching provider in reverse alias lookup

1 PR closed without merging

From the close comments: done elsewhere 1

  • #69967 fix(model-switch): guard explicit provider alias resolution · done elsewhere → ba7da13, ce6dd1a, #75262
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/14614.json
cluster/14614.md