Action status lost or misreported across restarts

NousResearch/hermes-agent · cluster 25916 · apps/desktop

Data as of 2026-10-22 12:15 UTC

4 open items. Fix merged in #79513. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 11 related items grouped here, 3 issues already closed.
Fix event: A fix was merged to main in PR #79513. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this partially resolved, deciding PR #79513. That is separate from the fix event.
Still open: 2 issues and 2 PRs.

Next step: read #79513, then check whether your report is one of the 2 still open.

Read #79513 Pick up a Lab task

These issues and fixes concern gateway/dashboard maintenance actions (especially backend updates and self-restarts) incorrectly reporting failure or losing status information when a process restarts. Work spans persistence of exit codes, terminal-state-driven reporting, and clearer messaging around disconnects.

Open issues2

Issue#25916Persist gateway maintenance action status instead of relying on in-memory process handles
Issue#41143Dashboard/TUI self-restart kills active Desktop session and shows opaque exit_code=-15

Open PRs2

PR#27565feat(web): persist gateway maintenance action status (phase 1) (#25916)
PR#41263fix(dashboard): explain embedded chat disconnects after restart

Fixes on record

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

#79513 fix(desktop): stop reporting false failure on successful backend updates

merged to main

files: apps/desktop/src/store/updates.test.ts, apps/desktop/src/store/updates.ts, apps/desktop/src/types/hermes.ts, hermes_cli/main.py, hermes_cli/update_cmd.py, hermes_cli/web_server.py, tests/hermes_cli/test_update_hangup_protection.py, tests/hermes_cli/test_web_server.py

3 PRs closed without merging

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

#47362 fix(desktop): don't report false failure on a successful backend update · superseded by another PR → #79513
#47928 fix(dashboard): persist action exit code across gateway restarts (#47864) · other
#65681 fix(desktop): make remote backend updates terminal-state driven · superseded by another PR → #79513, #52470

Closed issues · 3

Closed#47359Desktop: backend update reports "Backend update failed" even when the update succeeds
Closed#47864Dashboard reports "Action failed (exit ?)" after a successful `hermes update` (status lost across dashboard restart)
Closed#62118[Bug]: Dashboard shows "Action failed (?)" after successful self-update and systemd restart

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.14: 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: #79513
Closed issues: 3
Attempts: 3 PRs closed without merging
Fix link checked: 5 Aug 2026

For your agent

The same facts, typed.

cluster/25916.json
cluster/25916.md