Cairn

Fix route persistence during provider fallback

NousResearch/hermes-agent · cluster 121506 · 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 changes address how the originally requested route is stored and restored across provider fallback scenarios, ensuring that sessions, gateways, and the TUI correctly preserve and resume on the intended or fallback-picked model and provider rather than a transient live route.

Open issues1

  • Issue#121506Provider fallback is persisted into the session row, so resumed sessions keep running on the fallback (and the fallback inherits the primary's identity note)

Open PRs2

  • PR#121533fix(session): preserve requested route across provider fallback
  • PR#121629fix(tui): resume a fallback-served chat on its picked model and provider

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #121540 fix(gateway): persist the requested route, not a fallback turn's live route · superseded by another PR → #121506, #121533
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/121506.json
cluster/121506.md