Cairn
NousResearch/hermes-agent

MCP config watcher retry behavior on reload errors

Cluster 14716 · hermes cli. 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 members address a bug where the MCP config watcher incorrectly records unsuccessful reloads as successfully applied, causing it to stop retrying. The correction ensures unsuccessful reloads are not marked as applied so retries can continue.

Open issues1

  • Issue#14716MCP config watcher records failed reloads as applied and stops retrying

Open PRs1

  • PR#14855fix(cli): retry MCP config reload after failed apply

1 PR closed without merging

From the close comments: merged via another change 1

  • #14745 fix(cli): MCP config watcher retries after failed reload (#14716) · merged via another change
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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/14716.json
cluster/14716.md