NousResearch/hermes-agent

Desktop backend update falsely reporting failure on success

Cluster 47359 · apps/desktop. Data as of 2026-10-24 20:38 UTC

Nothing open on GitHub. Fix merged in #79513 on 5 Aug 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 #79513. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #79513. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #79513 Pick up a Lab task

The members concern the desktop app's remote backend update flow, where a "Backend update failed" message is reported even when the update succeeds. Three of the four are fix-oriented changes aiming to avoid false failure reports, one of which also mentions making updates terminal-state driven; the fourth is the issue describing the problem.

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.

#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

2 PRs closed without merging

From the close comments: superseded by another PR 2

#47362 fix(desktop): don't report false failure on a successful backend update · superseded by another PR → #79513
#65681 fix(desktop): make remote backend updates terminal-state driven · superseded by another PR → #79513, #52470

Closed issues · 1

Closed#47359Desktop: backend update reports "Backend update failed" even when the update succeeds

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

Subsystem: apps/desktop
Merged PRs: #79513
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 5 Aug 2026

For your agent

The same facts, typed.

cluster/47359.json
cluster/47359.md