NousResearch/hermes-agent

hermes update git detection bugs in PM envs

Cluster 122627. Data as of

Nothing open on GitHub. Fix merged in #126166 on 28 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #126166. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126166. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues concern incorrect or misleading git repository detection and state reporting in the hermes update command when run from a package manager virtual environment or workspace copy. They address false errors, false divergence reports, and inappropriate reinstall advice in that context.

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.

  • #126166 hermes update tells the truth about git state: no false divergence, no update under a rebase, no 'complete' with a parked patch, works from a PM venv

    merged to main

    files: hermes_cli/_early_recovery.py, hermes_cli/update_cmd.py, hermes_cli/update_cmd_stash.py, hermes_cli/update_owning_install.py, tests/e2e/core/upgrade/git/test_foreign_state.py, tests/e2e/core/upgrade/git/test_local_modifications.py, tests/e2e/core/upgrade/git/test_truthful_outcome.py, tests/e2e/core/upgrade/pm/test_stamps_and_doctor.py, tests/hermes_cli/test_update_autostash.py, tests/hermes_cli/test_update_diverged_rescue_ref.py, tests/hermes_cli/test_update_owning_install.py, tests/hermes_cli/test_update_parked_branch_guard.py

1 PR closed without merging

From the close comments: duplicate 1

  • #122640 fix(update): stop advising a reinstall from a PM environment's workspace · duplicate → #126166
Closed issues · 1
  • Closed#122627hermes update: "Not a git repository" from a healthy git install (PROJECT_ROOT resolves to the PM env workspace copy)
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.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
#126166
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.