Fix /reload-mcp diff to compare against config

NousResearch/hermes-agent · cluster 80771 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

A bug caused /reload-mcp to diff against live socket connections rather than the config file, incorrectly reporting still-configured servers as removed. These members address the fix for that diffing logic.

Open issues1

  • Issue#80771[Bug]: `/reload-mcp` reports still-configured servers as "➖ Removed" — the diff never reads config

Open PRs3

  • PR#80855fix(tools): diff /reload-mcp against config, not the connection registry
  • PR#94452fix(mcp): use config for /reload-mcp diff labels
  • PR#104051fix(gateway): ensure /reload-mcp diff reads config to avoid mislabeling servers as removed

2 PRs closed without merging

From the close comments: duplicate 2

  • #80794 fix(mcp): classify the /reload-mcp diff against config, not live sockets · duplicate → c452387, #80855, #80771
  • #80860 fix(cli): read MCP config to distinguish removed from not-connected servers (#80771) · duplicate → #80794
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.33: 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
2 PRs closed without merging

For your agent

The same facts, typed.