Cairn
NousResearch/hermes-agent

MCP server discovery timing in slash worker tools

Cluster 92330 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 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 1 PR.

These issues and PRs address a race condition where the /tools command in the slash worker could enumerate tools before MCP server discovery had completed, causing slow or still-connecting servers to be missing or dropped from the listing.

Open issues1

  • Issue#92330slash worker: /tools can list a catalog missing a still-connecting profile-local MCP server (no late-refresh in the worker process)

Open PRs1

  • PR#92340fix(tui): keep slow MCP servers visible in slash worker tools

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #94105 fix(tui): join MCP discovery in slash-worker /tools before enumerating · superseded by another PR → #104241
  • #104241 fix(tui): join MCP discovery in slash-worker /tools before enumerating · superseded by another PR → #94105, #92340, #92330
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.50: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/92330.json
cluster/92330.md