Cairn
NousResearch/hermes-agent

Prevent fallback provider leaking into composer model

Cluster 75320 · apps/desktop. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where the fallback provider was being incorrectly persisted or synced into the composer model atoms, causing new sessions to inherit the fallback as the primary provider. The fixes aim to keep fallback state isolated from composer model selection.

Open issues1

  • Issue#75320[Bug]: Desktop sticky-ises fallback provider as composer model — new sessions inherit the fallback as PRIMARY, defeating per-turn primary restoration

Open PRs1

  • PR#75518fix(desktop): stop syncing session runtime model/provider to composer atoms

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #75323 fix(desktop): keep fallback out of composer model · superseded by another PR → #102793
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.67: 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
apps/desktop
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/75320.json
cluster/75320.md