Cairn
NousResearch/hermes-agent

kanban default_assignee config hot-reload behavior

Cluster 55446 · gateway. 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 an issue where changes to the default_assignee configuration require a gateway restart to take effect. The proposed fix involves re-reading the value from config on each dispatcher tick rather than caching it at startup.

Open issues1

  • Issue#55446fix(kanban): default_assignee config changes require gateway restart to take effect

Open PRs1

  • PR#55678fix(kanban): re-read default_assignee from config on each dispatch tick

1 PR closed without merging

From the close comments: done elsewhere 1

  • #55513 fix(kanban): reload default_assignee on each dispatcher tick · done elsewhere → #55678, #55446
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/55446.json
cluster/55446.md