NousResearch/hermes-agent
Fix managed SSH update receipt correlation_id reporting
Cluster 101516 · hermes cli. Data as of
1 open item. Fix merged in #126989 on 29 Sep 2026. Check it covers your case.
The short answer
0open issues
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #126989. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126989. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where Desktop managed SSH updates always report failure because the backend never writes the correlation_id to the update receipt. The fixes involve recording the correlation_id correctly and preventing successful updates from being misreported as failures.
Open issues0
Open PRs1
- PR#101539fix(update): stop successful managed SSH updates reporting failure
Fixes on record
-
#126989 fix(update): record Desktop's correlation_id in the update receipt
files:
hermes_cli/update_receipt.py,tests/hermes_cli/test_update_receipt.py
Closed issues · 1
- Closed#101516Desktop managed SSH update always reports failure: backend never writes receipt correlation_id
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.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #126989
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 29 Sep 2026