hermes - 💡(How to fix) Fix [Bug]: windows bug [1 participants]

Bug Description

[Windows] Multiple Windows Compatibility Issues

Hermes Gateway version: (fill in your version) OS: Windows 10/11 (PowerShell)

Issue 1: Phantom PID - Gateway reports "already running" after clean shutdown

Description: After fully closing Hermes Gateway, a phantom process remains. Restarting Hermes reports "already running (PID XXXX)" even though the process is not visible in Task Manager.

Workaround: Kill the process manually via Task Manager or taskkill /PID XXXX.

Issue 2: Update fails - pip install -e causes path corruption

Description: Running hermes update (which internally calls pip install -e) corrupts the installation path, causing import errors or missing modules on next launch.

Affected files/modules: The editable install path breaks after self-update.

Issue 3: WebUI build fails - Unix commands not compatible with PowerShell

Description: The web/package.json scripts use Unix commands (rm -f, cp, etc.) which are not available in PowerShell on Windows. hermes webui or hermes build-webui fails immediately.

Affected command: hermes webui / hermes build-webui

Issue 4: os.kill() failure - Windows doesn't support signals

Description: When stopping/restarting the Gateway, Hermes uses os.kill(pid, signal) which does not work on Windows. This causes child processes to leak and not clean up properly.

Affected operation: Gateway shutdown, restart, update

Issue 5: Terminal tool silently returns empty output

Description: In some sessions, the terminal tool returns exit_code: 0 but both stdout and stderr are completely empty. Commands appear to succeed but produce no output, making the terminal unusable.

Reproduction: Unclear - appears intermittently across sessions.

Environment

• Windows version: (e.g., Windows 11 23H2)
• Shell: PowerShell
• Hermes version: (run hermes --version)
• Python version: (run python --version)

Expected behavior

All features should work on Windows without requiring workarounds or manual fixes.

Additional context

These issues have been individually fixed multiple times by community contributors but keep recurring or regressing after updates. A sustained effort to maintain Windows compatibility (e.g., CI testing on Windows, or a Windows-specific test suite) would help prevent future regressions.

Steps to Reproduce

Windows 更新

Expected Behavior

更新成功

Actual Behavior

失败

Affected Component

Gateway (Telegram/Discord/Slack/WhatsApp)

Messaging Platform (if gateway-related)

No response

Debug Report

⚙️  /debug
⚠️  This will upload the following to a public paste service:
  • System info (OS, Python version, Hermes version, provider, which API keys
    are configured — NOT the actual keys)
  • Recent log lines (agent.log, errors.log, gateway.log — may contain
    conversation fragments and file paths)
  • Full agent.log and gateway.log (up to 512 KB each — likely contains
    conversation content, tool outputs, and file paths)

Pastes auto-delete after 6 hours.

Operating System

Windows 11

Python Version

No response

Hermes Version

0.11.0

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR