Cairn

Docker/terminal venv PATH loss in login shells

NousResearch/hermes-agent · cluster 9792 · environments

Data as of

6 open items. Fix attempted, not merged.

The short answer

2open issues
4open PRs
12items grouped
Known?
Yes. 12 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 4 PRs.

A cluster of bugs and fixes centered on the Python virtual environment being dropped from PATH during Docker exec sessions and login-shell snapshots, particularly on Debian-based images. Related fixes address making the hermes entrypoint accessible and preserving venv PATH across shell initialization sequences.

Open issues2

  • Issue#56634[Bug]: terminal tool's bash -l session snapshot loses venv PATH on Debian-based images (/etc/profile resets it before /etc/profile.d/)
  • Issue#66642[Bug]: Terminal tool loses the venv from PATH — the login-shell session snapshot resets it

Open PRs4

  • PR#56642fix(terminal): preserve venv PATH in login-shell snapshot on Debian
  • PR#64849fix(docker): restore the venv on PATH for login shells on Debian
  • PR#87738fix(terminal): restore venv PATH before the login-shell snapshot dump
  • PR#130801fix(terminal): retry unresolved Hermes launcher discovery

3 PRs closed without merging

From the close comments: other 3

  • #18674 fix(docker): expose hermes entrypoint on PATH · other
  • #23205 Fix/docker exec hermes path · other
  • #66902 fix(tools): preserve active venv on PATH across login-shell snapshots (#66642) · other → #66642
Closed issues · 3
  • Closed#9792[Bug]: hermes command not found in external interactive shells after virtualenv migration (#8226)
  • Closed#18673[Bug]: hermes command not found during docker exec (requires absolute virtual environment path)
  • Closed#32619[Bug]: tool execute_code no longer inherits from the machine's environment
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.14: 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
environments
Closed issues
3
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/9792.json
cluster/9792.md