Cairn
NousResearch/hermes-agent

Agent fallback chain behavior: api_mode, reset, cooldown

Cluster 57582 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These members all concern the agent's fallback handling. Topics include respecting explicit api_mode overrides, a fallback index not resetting after primary recovery, and bounding an exhaustion cooldown while keeping a replay throttle. The titles show related themes but do not establish one single shared problem.

Open issues1

  • Issue#57582Fallback chain (_fallback_index) doesn't reset on primary recovery — mid-session exhaustion silently disables failover for rest of session

Open PRs2

  • PR#16346fix(agent): respect fallback api_mode overrides
  • PR#57700fix(agent): gate exhaustion cooldown to bounded window, preserve #24996 replay throttle

1 PR closed without merging

From the close comments: duplicate 1

  • #57957 [codex] fix(fallback): honor explicit api_mode · duplicate → #16346, #29749, #57582, #57700
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/57582.json
cluster/57582.md