NousResearch/hermes-agent

Orphaned isolated serve backends idle-exit and lock fixes

Cluster 101626. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #103723 on 5 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #103723. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #103723. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #103723, then check it covers your case.

Read #103723 Pick up a Lab task

These items address orphaned SSH-isolated serve backends that accumulate without clients, including idle-exit behavior, multi-writer state.db corruption risk, and lock claim handling for orphan reaping.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#103723 serve: Desktop-over-SSH isolated backends exit on their own when no client is connected (#101626, salvage #101678)

merged to main

files: contributors/emails/[email protected], hermes_cli/web_server.py, hermes_cli/web_server_idle_exit.py, tests/hermes_cli/test_web_server_idle_exit.py, website/docs/user-guide/configuration.md

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

#101678 fix(serve): idle-exit orphaned SSH-isolated backends and refuse a second writer · superseded by another PR → f77e2a5, #103723
#101721 fix(serve): withdraw orphan-reap immunity from a disproved lock claim · other → 5996d12, 6327930, c524552, 48a0034, #101626, #101678, #101721

Closed issues · 1

Closed#101626[Bug]: A sleeping laptop silently accumulates orphaned remote `serve --isolated` backends — multi-writer `state.db` corruption, not just process leak

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

Merged PRs: #103723
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 5 Sep 2026

For your agent

The same facts, typed.

cluster/101626.json
cluster/101626.md