NousResearch/hermes-agent

Fix launchers misbound to foreign HERMES_HOME

Cluster 123238 · hermes cli. Data as of

1 open item. Fix merged in #132521 on 4 Oct 2026. Check it covers your case.

The short answer

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

A bug where launching Hermes under a different HERMES_HOME incorrectly rebinds shared launchers to that environment's Python, potentially bricking the checkout if that home is later deleted. The fixes ensure a borrowed HERMES_HOME leaves the original checkout's launchers untouched.

Open issues0

No open issues.

Open PRs1

  • PR#128579fix(install,update): a borrowed HERMES_HOME leaves the checkout alone; the macOS update panel shows progress

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #132521 fix(cli,pm): a borrowed HERMES_HOME leaves the shared checkout's launchers and tail to its owner

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/_launchers.py, hermes_cli/venv_sync.py, pm/environments.py, tests/hermes_cli/test_borrowed_home_launch.py, tests/hermes_cli/test_hermes_home_shared_launchers.py

2 PRs closed without merging

From the close comments: merged via another change 1 · other 1

  • #123887 fix(cli): keep shared launchers off foreign HERMES_HOME interpreters · merged via another change → #132521, #128579
  • #132688 fix(launchers): keep foreign-home interpreter pins instead of rebinding shared launchers (fixes #123238) · other → 353b843
Closed issues · 1
  • Closed#123238[Bug]: Launching under a different HERMES_HOME rebinds the checkout's shared launchers to that home's Python; a deleted temp home then bricks hermes
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.40: 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
#132521
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
4 Oct 2026

For your agent

The same facts, typed.