hermes - 💡(How to fix) Fix PATH injection from venv shadows system Python with outdated 3.11

Problem

The hermes-agent installation adds its venv bin/ directory to the front of $PATH via .bashrc:

export PATH="$HERMES_HOME/hermes-agent/venv/bin:$PATH"

This venv was created by uv with cpython-3.11 (~/.local/share/uv/python/cpython-3.11-linux-x86_64-gnu/), which means:

• python3 now resolves to 3.11 instead of the system's 3.13
• pip resolves to 3.11's bundled pip 24.0 instead of the system pip 26.x
• Any python3 -m venv creates venvs with 3.11 instead of the expected system Python
• This affects all shells and all projects, not just hermes-agent

Environment

• Debian Trixie/Forky
• System Python: 3.13 (/usr/bin/python3)
• Hermes venv Python: 3.11 (uv-installed cpython)

Expected behavior

The hermes-agent venv should not globally shadow the system Python. Options:

1. Don't prepend the venv bin/ to global $PATH — use a wrapper script or alias for hermes commands instead
2. If PATH modification is necessary, append instead of prepend
3. Use the system Python version when creating the venv instead of pinning to 3.11

Impact

Every other Python project on the system silently gets the wrong Python version and an outdated pip, leading to confusing version mismatches and broken venv creation.