fix(terminal): strip PYTHONHOME/PYTHONPATH from subprocess env

[carterwayneskhizeine]

Summary

On Windows, Hermes Agent bootstraps its own Python via uv and sets PYTHONHOME in the process environment. When the terminal tool spawns subprocesses, this PYTHONHOME is inherited, causing conda (and potentially other Python-based tools) to load uv's Python instead of the system/conda Python — resulting in No module named conda.

Fix

Strip PYTHONHOME and PYTHONPATH from the subprocess environment in _make_run_env(). This mirrors the unset PYTHONHOME / unset PYTHONPATH logic already present in install.sh at launch time.

run_env.pop("PYTHONHOME", None)
run_env.pop("PYTHONPATH", None)

Testing

After patching, conda --version returns conda 25.5.1 correctly in the Hermes Agent terminal session on Windows.

Checklist

• Tests pass (if applicable)
• Documentation updated (if applicable)
• scripts/install.sh Python-path sanitization is already in place

[teknium1]

Thanks for identifying the inherited Python-runtime environment hazard. The foreground fix needs a small salvage for the current terminal architecture.

Problems

• The proposed change only covers foreground LocalEnvironment._run_bash, which builds _make_run_env() at tools/environments/local.py:1004. Background and PTY terminal spawns instead call _sanitize_subprocess_env() at tools/process_registry.py:718 and tools/process_registry.py:760; that helper currently copies allowed variables at tools/environments/local.py:355-361 and removes only VIRTUAL_ENV/CONDA_PREFIX at :383-384.
• The diff contains no regression test. tests/tools/test_local_env_blocklist.py:289-304 already provides the matching pattern of asserting stripping from both environment constructors.

Suggested changes

• Apply the Python-runtime-variable scrub to both terminal environment builders and add tests for foreground plus background/PTY construction.

Automated hermes-sweeper review.

[teknium1]

Please apply the same scrub to _sanitize_subprocess_env: background and PTY terminal calls use it at tools/process_registry.py:718 and :760, while this change protects only the foreground _make_run_env path.

[teknium1]

Partial update: the PYTHONPATH half of this is now fixed on main via #88182 (selective strip of Hermes-owned entries from all subprocess env builders, preserving user-set paths). The PYTHONHOME half is NOT yet covered on main — that's in scope for the consolidation under review in #82581. Leaving this open until PYTHONHOME stripping lands; if #82581 covers it, this will be closed with credit then.

[teknium1]

Both halves of this PR are now fixed on main: the PYTHONPATH strip landed in #88182, and the PYTHONHOME strip — which you were the first to report and propose, back in May — landed today in #88285 (as part of the ownership-model consolidation from #82581). The merged approach strips both selectively rather than the blanket pop proposed here, so user-set entries survive, but your conda repro was the original driver for the PYTHONHOME half. Thank you @carterwayneskhizeine — closing as completed on main.