Cross-profile TERMINAL_* env leak and session loading
NousResearch/hermes-agent · cluster 102769
Data as of
Nothing open on GitHub. Fix merged in #103625. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #103625. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #103625. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Most members address a cross-profile environment variable leak where TERMINAL_* settings from one routed profile bleed into the shared process environment during multi-profile serve. One unrelated member concerns guaranteeing initial session load on app mount.
Open issues0
Open PRs0
Fixes on record
-
#103625 fix(env): multi-profile serve no longer leaks a routed profile's terminal backend into the shared process env (#102769, salvage #97014)
files:
hermes_cli/env_loader.py,tests/hermes_cli/test_terminal_bridge_profile_scope.py
5 PRs closed without merging
From the close comments: done elsewhere 2 · duplicate 1 · merged via another change 1 · other 1
-
#102392 fix(desktop): guarantee initial session load on app mount (#101843) · other →
#101843,#102769,#125530 - #102800 fix(env): prevent cross-profile TERMINAL_* leak in multi-profile serve (#102769) · done elsewhere
-
#102932 fix(env): prevent cross-profile TERMINAL_* leak in multi-profile serve (#102769) · merged via another change →
#102800 -
#103512 fix: Cross-profile TERMINAL_* leak in multi-profile serve: cron tick pins a routed profile's docker backend into os.environ, hijacking the launch profile's sessions (#102769) · done elsewhere →
2e24e06,#102769,#103625,#97014 -
#103672 fix(env): prevent cross-profile TERMINAL_* leak in multi-profile serve (#102769) · duplicate →
#103625,#102800,#102932
Closed issues · 1
- Closed#102769Cross-profile TERMINAL_* leak in multi-profile serve: cron tick pins a routed profile's docker backend into os.environ, hijacking the launch profile's sessions
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.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #103625
- Closed issues
- 1
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 5 Sep 2026