Cairn
NousResearch/hermes-agent

Agent init fallback failures: logging and isolation fixes

Cluster 119533 · agent. Data as of

1 open item. Fix merged in #121480 on 24 Sep 2026. Check it covers your case.

The short answer

0open issues
1open PR
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #121480. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #121480. That is separate from the fix event.
Still open
0 issues and 1 PR.

These items address how the agent handles and reports provider/fallback failures at initialization time, including surfacing clearer error reasons, adjusting log severity, and preventing auxiliary failures from disabling the primary chat path.

Open issues0

No open issues.

Open PRs1

  • PR#119544fix(agent): keep auxiliary failures from disabling single-key chat

Fixes on record

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

  • #121480 fix(agent): say why init-time provider resolution failed (pool exhausted, refused fallbacks)

    merged to main

    files: agent/agent_init.py, tests/agent/test_init_fallback_refusal_warning.py

3 PRs closed without merging

From the close comments: closed without comment 1 · merged via another change 1 · superseded by another PR 1

  • #119550 fix(agent): surface why every init-time fallback entry refused · merged via another change → 13141c6, #121480, #119533
  • #119555 fix(aux): unverified payment-shaped errors bench briefly instead of an hour · closed without comment
  • #120255 fix(agent): escalate init-time fallback failure log from debug to warning (#119533) · superseded by another PR → 13141c6, #121480, #119533, #119550
Closed issues · 1
  • Closed#119533Single-entry OpenRouter credential-pool burn turns into recurring 'No LLM provider configured' turn-killer until gateway restart
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.33: 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
#121480
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/119533.json
cluster/119533.md