Cairn
NousResearch/hermes-agent

Curator fallback chain config not propagated correctly

Cluster 78371 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 configured fallback chains for the curator were not being forwarded or propagated through the review process. The work involves fixes to ensure per-task fallback chain settings are correctly passed along rather than ignored.

Open issues1

  • Issue#78371Curator review: per-task fallback_chain (auxiliary.curator.fallback_chain) is ignored

Open PRs1

  • PR#79750fix(review): propagate configured curator fallback chains

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #89498 fix(curator): forward configured fallback chains · superseded by another PR → #79750
  • #93664 fix(agent): honor auxiliary.fallback_chain in review forks · superseded by another PR → #79750, #93592
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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/78371.json
cluster/78371.md