Cairn
NousResearch/hermes-agent

False failure reporting on no-op backend updates

Cluster 58764 · apps/desktop. Data as of

Nothing open on GitHub. Fix merged in #79513. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 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.

These items address a bug where the desktop client incorrectly reports a backend update failure when the backend is already up to date and no actual update is needed. Fixes span the CLI output, update logic, and terminal-state handling.

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

3 PRs closed without merging

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

  • #59190 fix(update): treat no-op backend updates as success · superseded by another PR → #79513, #58764
  • #59198 fix(cli): print '✓ Update complete!' on the Already up to date path · duplicate → #59190, #58764
  • #65681 fix(desktop): make remote backend updates terminal-state driven · superseded by another PR → #79513, #52470
Closed issues · 1
  • Closed#58764Desktop shows 'Backend update failed' after successful update (no-op 'Already up to date' path)
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.40: 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
3 PRs closed without merging
Fix link checked
5 Aug 2026

For your agent

The same facts, typed.

cluster/58764.json
cluster/58764.md