Hermes2 (PC Hermes)
Instance
- Running on: Windows PC (DESKTOP-F9KSPPP)
- Location:
D:\Hermes Termux\hermes2\
- Purpose: PC-side Hermes agent; connected to by OpenClaw monitor scripts
Port
- Default port: 9119 (backend API)
- When running:
netstat -ano | findstr "9119" should show LISTENING
Relationship with OpenClaw
- OpenClaw monitor script tries to connect to “Hermes” (PC Hermes/Hermes2)
- When Hermes2 is NOT running, monitor logs show:
Hermes 连接失败
- This causes OpenClaw to fall back to automated monitor mode instead of interactive Telegram DM
Startup
- Check if running:
tasklist /fi "imagename eq python*" on PC
- Check port 9119:
netstat -ano | findstr "9119" on PC
- If not running, start via WSL or Windows Python
Distinction from Hermes (Termux)
| Hermes (Termux) | Hermes2 (PC) |
|---|
| Platform | Termux/Android | Windows PC |
| Port | 8000 (gateway) | 9119 (API) |
| Location | ~/.hermes/ | D:\Hermes Termux\hermes2\ |
| Purpose | Primary agent | PC-side agent |
Troubleshooting
- “Hermes 连接失败” in OpenClaw monitor: Check if Hermes2 process is running on PC
- Telegram DM not responding: If Hermes2 is down, OpenClaw can’t route messages properly