Cairn
NousResearch/hermes-agent

Credential pool matching for named custom providers

Cluster 45715 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
6items grouped
Known?
Yes. 6 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
1 issue and 1 PR.

Members appear to concern a mismatch between bare 'custom' and named 'custom:<name>' providers, which may cause credential pool lookup or rotation to be skipped. Most are proposed agent-side fixes (matching on requested provider name, or tolerating config load failure), plus issue reports describing the mismatch and related 503 errors.

Open issues1

  • Issue#45715[BUG] Credential pool mismatch: agent.provider resolves to bare 'custom' even when requested_provider is named, causing pool mutation skip + 503 across primary + subagent + bg-review paths

Open PRs1

  • PR#45763fix(agent): match custom credential pools via agent.requested_provider

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #45289 fix(agent): credential-pool recovery for custom providers (custom vs custom:<name> mismatch)

    merged to mainSuggested link · files and diff not shown

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #45819 fix(agent): match custom credential pools by requested provider name · duplicate → #45763, #45715, #45823
  • #45823 fix(agent): accept custom pool match when config loading fails (#45715) · other
Closed issues · 1
  • Closed#47272Credential pool provider mismatch for custom:* providers — pool rotation silently skipped
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
Merged PRs
#45289
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/45715.json
cluster/45715.md