NousResearch/hermes-agent

Update command failures and ancestry probe handling

Cluster 138716 · hermes cli. Data as of 2026-10-24 20:38 UTC

Nothing open on GitHub. Fix merged in #139079 on 15 Oct 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 #139079. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #139079 Pick up a Lab task

One bug report describes an update failing so that a new install was needed, and two fix PRs change how the update logic handles a merge-base/ancestry probe that hangs or cannot answer (falling back to GitHub, or treating the relation as unknown). The titles suggest these are related, but they do not confirm that the PRs address the reported bug.

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.

#139079 hermes update no longer refuses the stable channel when git is slow to find the unfetched release (#137646, salvage #137649)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/source_releases.py, tests/hermes_cli/test_gateway_chat_native.py, tests/hermes_cli/test_stable_forward_only_shallow.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · partial fix 1

#138722 fix(update): treat an ancestry probe that cannot answer as an unknown relation · partial fix → #137649, #138427, #138404
#138724 fix(update): a hung merge-base probe falls back to GitHub instead of aborting · done elsewhere → 3bdb82d, #139079, #137649

Closed issues · 1

Closed#138716[Bug]: update failed, must new install

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: hermes cli
Merged PRs: #139079
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 15 Oct 2026

For your agent

The same facts, typed.

cluster/138716.json
cluster/138716.md