NousResearch/hermes-agent
Windows desktop MCP child processes lingering after exit
Cluster 132069 · apps/desktop. 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskOne issue reports that the desktop app leaves MCP child processes running after exit. Two members share an identical pull request title about declaring winapi signatures and dropping SILENT_BREAKAWAY_OK so a kill-on-close job works on Windows, which appears related but whose outcome is not stated here.
Open issues1
- Issue#132069Desktop leaves MCP child processes running after exit
Open PRs1
- PR#137860fix(win32): declare winapi signatures and drop SILENT_BREAKAWAY_OK so the kill-on-close job works
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#135689 fix(win32): declare winapi signatures and drop SILENT_BREAKAWAY_OK so the kill-on-close job works · superseded by another PR →
#137860
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.00means 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 LabAt a glance
- Subsystem
- apps/desktop
- Closed issues
- 0
- Attempts
- 1 PR closed without merging