Hi team, thank you for building and maintaining Hermes Agent! It has been an incredibly useful tool for my daily workflow. I'd like to contribute a small fix to the setup script.

The install_open_webui function correctly resolved the python interpreter into the $py variable, but hardcoded 'python' in subsequent pip install commands. This caused 'command not found' or 'externally-managed-environment' errors on systems where 'python' is not implicitly aliased to 'python3'.

What does this PR do?

This PR fixes a bug in the Open WebUI bootstrap script where the Python interpreter was hardcoded as python during the virtual environment package installation. By replacing the hardcoded python command with the dynamically resolved "$py" variable, the script now consistently targets the correct Python executable across different environments (especially on macOS or Linux where python is not always aliased to python3).

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• Changed python to "$py" in the install_open_webui function within scripts/setup_open_webui.sh to ensure pip install commands run inside the correct virtual environment context.

How to Test

1. Run the script in an environment where the python command is not implicitly aliased to python3 (or Homebrew's externally managed environment is strictly enforced).
2. Execute bash scripts/setup_open_webui.sh.
3. Verify that the Open WebUI virtual environment is successfully created and open-webui is installed without throwing command not found or PEP 668 externally-managed-environment errors.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (N/A: This is a fix for a bash installer script)
• I've tested on my platform: macOS (Apple Silicon)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Screenshots / Logs

Before:

[open-webui-bootstrap] Installing Open WebUI into a dedicated virtualenv...
[open-webui-bootstrap] Using Python interpreter: python3
scripts/setup_open_webui.sh: line 166: python: command not found

After:

[open-webui-bootstrap] Installing Open WebUI into a dedicated virtualenv...
[open-webui-bootstrap] Using Python interpreter: python3
...
Successfully installed open-webui...