NousResearch/hermes-agent
MCP reconnect causes stale registry state
Cluster 126978 · mcp. 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug where reconnecting to MCP without parking fails to properly resync the tool registry, leaving removed tools present and ignoring new tools or schema changes. Two fix attempts address this resync behavior.
Open issues1
- Issue#126978[Bug]: MCP reconnect without parking re-discovers tools but keeps the stale registry (removed tools stay, new tools/schema changes ignored)
Open PRs1
- PR#127124fix(mcp): resync registry on reconnect without parking
1 PR closed without merging
From the close comments: other 1
-
#127004 fix(mcp): resync registry on reconnect without parking · other →
#127124
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.00means 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 LabAt a glance
- Subsystem
- mcp
- Closed issues
- 0
- Attempts
- 1 PR closed without merging