Cairn
NousResearch/hermes-agent

Custom provider subname lost in credential pool lookup

Cluster 29872 · hermes cli. 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 members appear to concern the same topic: a provider value like custom:<subname> being normalized to bare 'custom' during credential pool lookup, which may cause the wrong API key to be selected. Two are pull requests proposing a fix to preserve the subname, and one is a bug report describing the behavior in model_aliases.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · other 1

  • #29893 fix(auth): preserve custom:<subname> in credential pool lookup (fixes #29872) · closed without comment
  • #33700 fix(auth): preserve custom:<subname> in credential pool lookup · other → e38ea38, #29872
Closed issues · 1
  • Closed#29872[Bug]: model_aliases provider: custom:<subname> normalized to bare 'custom', wrong API key picked from pool
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/29872.json
cluster/29872.md