Cairn
NousResearch/hermes-agent

Notify users when credential pool exhaustion triggers provider fallback

Cluster 10476 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 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.

All four members concern the same topic: a notification being emitted when credential pool exhaustion leads to a fallback or provider switch. One is a bug report describing the fallback as silent and inconsistent with fallback_model notifications, and the other three are fix-oriented titles addressing it.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1 · other 1

  • #10479 fix: emit notification on credential pool exhaustion before fallback · closed without comment
  • #10480 fix(agent): notify gateway users when credential pool auth exhaustion causes provider switch · superseded by another PR → 3fe7f6d
  • #10716 fix(agent): notify when credential-pool exhaustion activates fallback · other → 3fe7f6d, #10718
Closed issues · 1
  • Closed#10476[Bug]: Credential pool provider fallback is silent — inconsistent with fallback_model notification behavior
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.50: 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
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/10476.json
cluster/10476.md