Cairn
NousResearch/hermes-agent

Named profiles incorrectly killing SSH-owned serves

Cluster 94032 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 2 PRs.

These items address a bug where named-profile startup orphan reaping scans the wrong scope, causing named profiles to kill serves that are owned by SSH connections rather than the profile itself.

Open issues0

No open issues.

Open PRs2

  • PR#94039fix(cli): stop named profiles from killing SSH-owned serves
  • PR#103732fix(cli): stop named profiles from killing SSH-owned serves
Closed issues · 1
  • Closed#94032Desktop SSH: startup orphan reaper scans profile-scoped HERMES_HOME for machine-scoped ownership locks — named-profile serves kill remote isolated serves
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
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/94032.json
cluster/94032.md