NousResearch/hermes-agent

Background review fork runtime inheritance bug

Cluster 105825 · agent. 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 concern a bug where background review or curator fork processes incorrectly inherit the fallback runtime/model instead of the primary one. The work addresses how runtime selection is propagated during or after primary failover scenarios.

Open issues1

  • Issue#105825Background review/curator turns inherit fallback model after primary failover recovery

Open PRs1

  • PR#105835fix(#105825): background review fork inherits primary, not fallback runtime

1 PR closed without merging

From the close comments: duplicate 1

  • #105830 fix(review): pin background-review fork to primary runtime during fallback (#105825) · duplicate → #105835
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.