NousResearch/hermes-agent

Update logic fixes for branch-switch checkout handling

Cluster 125685. Data as of 2026-10-24 20:38 UTC

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

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

Read #126206 Pick up a Lab task

These items address bugs in the update command where switching branches during an update incorrectly reports 'Already up to date' or loses track of the running checkout. The fixes involve preserving the running checkout, correcting commit counting, and separating branch-switch movement from rollback state.

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.

#126206 fix(update): count from the running checkout and roll back to it after a branch switch

merged to main

files: hermes_cli/update_cmd.py, tests/hermes_cli/test_update_existing_branch_baseline.py, website/docs/getting-started/updating.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#125728 fix(update): preserve the running checkout across branch-switch updates · merged via another change → #126206, #125771
#125771 fix(update): separate branch-switch movement from rollback state · superseded by another PR → #126206, #125728

Closed issues · 1

Closed#125685hermes update reports "Already up to date" after switching a detached checkout to an existing local main

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

Merged PRs: #126206
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 28 Sep 2026

For your agent

The same facts, typed.

cluster/125685.json
cluster/125685.md