NousResearch/hermes-agent

Scope dashboard stop to its own Hermes home

Cluster 113978. Data as of

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

The short answer

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

A bug where hermes dashboard --stop killed all Hermes dashboard/serve processes on the machine, not just those belonging to the caller's profile or HERMES_HOME. The fixes scope the stop behavior to only affect the relevant Hermes home's backend.

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.

  • #114803 fix(dashboard): --stop and the update sweep stop only this home's backend, sparing foreign installs and the caller's shell (#113978, salvage #113982 #113994)

    merged to main

    files: hermes_cli/dashboard_procs.py, hermes_cli/main.py, hermes_cli/main_dashboard.py, hermes_cli/profiles.py, hermes_cli/update_cmd_maint.py, tests/hermes_cli/test_dashboard_lifecycle_flags.py, tests/hermes_cli/test_dashboard_stop_spare_caller.py, tests/hermes_cli/test_resource_limits.py, tests/hermes_cli/test_stale_pid_guard.py, tests/hermes_cli/test_update_stale_dashboard.py, website/docs/reference/cli-commands.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #113982 fix(cli): scope dashboard stop to its Hermes home · merged via another change → df82862, #114803, #113978, #113982, #113994
  • #113991 fix(dashboard): scope --stop kills to the caller's HERMES_HOME · superseded by another PR → df82862, #114803, #113978, #113982, #113994
Closed issues · 1
  • Closed#113978[Bug]: hermes dashboard --stop kills every hermes dashboard/serve on the machine, not just its own profile
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
#114803
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.