Cairn
NousResearch/hermes-agent

launchd port-holder orphan handling during updates

Cluster 121596 · 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 items concern a recurring conflict during updates where launchd-managed port-holder processes are incorrectly identified or left unsupervised, causing an orphaned process to re-acquire the port and hold it without a token for an extended period. The work focuses on attribution logic and keeping the port holder under launchd supervision across kickstart cycles.

Open issues1

  • Issue#121596[Bug]: update kill/respawn fight on launchd-served fixed port (same-home variant): orphan re-orphaned every update, token-less impostor holds port for minutes

Open PRs1

  • PR#127277fix(update): keep a launchd-owned port holder supervised through kickstart -k

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #121784 fix(update): attribute launchd orphans by backend shape, not launcher spelling · superseded by another PR
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/121596.json
cluster/121596.md