NousResearch/hermes-agent

Fix branch resolution on narrow single-branch clones

Cluster 125112. Data as of 2026-10-24 13:18 UTC

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

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

Read #125631 Pick up a Lab task

These issues and fixes address a bug where hermes update incorrectly reports an existing branch as missing when operating on narrow or tag-pinned --single-branch clones. The fixes involve materialising or resolving the remote branch ref explicitly in such environments.

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.

#125631 fix(update): narrow tag-pinned clones update instead of reporting main missing

merged to main

files: hermes_cli/update_cmd.py, hermes_cli/update_cmd_check.py, hermes_cli/update_cmd_git.py, scripts/install.ps1, scripts/install.sh, tests/hermes_cli/test_update_narrow_clone_compare_ref.py, tests/hermes_cli/test_update_narrow_clone_refspec.py

2 PRs closed without merging

From the close comments: merged via another change 2

#125123 fix(updater): resolve compare ref on narrow (tag-pinned --single-branch) clones · merged via another change → #125631
#125132 fix(update): materialise origin/<branch> on narrow clones via explicit refspec · merged via another change → #125112, #125123, #125631

Closed issues · 1

Closed#125112[Bug]: `hermes update` cannot resolve `origin/<branch>` on a narrow clone (tag-pinned / `--single-branch`) — reports an existing branch as missing

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: #125631
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 27 Sep 2026

For your agent

The same facts, typed.

cluster/125112.json
cluster/125112.md