Cairn
NousResearch/hermes-agent

MCP reload via control socket or signal

Cluster 110976 · 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 discuss adding the ability to trigger an MCP reload through a control socket or signal, without requiring a chat message. The group covers a feature request and two related implementation efforts around this mechanism.

Open issues1

  • Issue#110976Feature request: expose MCP reload via signal or control-socket (no chat message needed)

Open PRs1

  • PR#110992feat(gateway): reload mcp from the control socket

1 PR closed without merging

From the close comments: done elsewhere 1

  • #110980 feat(gateway): reload MCP via control socket · done elsewhere → #110976, #110992
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/110976.json
cluster/110976.md