Cairn
NousResearch/hermes-agent

Stale or duplicate dashboard/backend processes and startup cleanup

Cluster 39136 · apps/desktop. Data as of

3 open items. Fix merged in #92775 on 23 Aug 2026. Check it covers your case.

The short answer

1open issue
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #92775. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

Most members concern stale, orphaned, or duplicate Hermes dashboard/backend processes (including --tui) and proposed or discussed startup cleanup to reap them. One member touches a related edge case where concurrent Bot Mode profile startups over SSH might reap each other.

Open issues1

  • Issue#39136Bug: stale `hermes dashboard --tui` processes accumulate across updates, not cleaned

Open PRs2

  • PR#39190fix(cli): clean stale dashboard processes on startup and broaden TUI pattern detection
  • PR#39197fix(dashboard): clean stale processes at dashboard startup (#39136)

Fixes on record

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

  • #92775 fix(desktop): concurrent Bot Mode profile startups no longer mutually reap over SSH (#92008, salvage #91994)

    merged to main

    files: hermes_cli/dashboard_procs.py, tests/hermes_cli/test_orphan_desktop_serve_reap.py

1 PR closed without merging

From the close comments: done elsewhere 1

  • #64344 fix(desktop): reap orphaned backends on startup to prevent duplicate sessions (#64304) · done elsewhere → 6386c75, 888624a, #92775
Closed issues · 1
  • Closed#64304Hermes One Desktop: Multiple dashboard processes causing duplicate sessions and message loss
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: 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
apps/desktop
Merged PRs
#92775
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
23 Aug 2026

For your agent

The same facts, typed.

cluster/39136.json
cluster/39136.md