Cairn

isolated serve wrongly claims host rendezvous record

NousResearch/hermes-agent · cluster 120165 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

A bug where hermes serve --isolated claims the host rendezvous record and blocks hermes dashboard from starting, plus two corresponding fixes to prevent isolated backends from claiming that record.

Open issues1

  • Issue#120165[Bug]: a supervised `hermes serve --isolated` wins the host rendezvous record and permanently blocks a supervised `hermes dashboard` — `--isolated` gates attach but not claim, `Refusing to start` (exit 1)

Open PRs2

  • PR#120188fix(rendezvous): let dashboard start beside isolated serve
  • PR#124771fix(cli): stop an --isolated backend from claiming the host record
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/120165.json
cluster/120165.md