# Hermes on Dankclaw operations

Use this when Hermes, Hermes WebUI, dashboard, Signal, or Gemma/FLM auxiliary routing is involved.

Facts:
- Host: Dankclaw 192.168.0.143.
- Live data: /home/dank/hermes-data mounted as /data.
- HERMES_DATA_DIR and HERMES_HOME must point to /data.
- Repo config.yaml.example is sanitized only; preserve live secrets and generated state.
- WebUI has listened on port 8787. Dashboard uses 9119. Chrome DevTools Protocol binds to 127.0.0.1:9222.
- Signal HTTP adapter expects signal-cli-daemon on 127.0.0.1:8080.

Health/status check:
- ssh dankclaw 'for u in hermes hermes-webui hermes-dashboard signal-cli-daemon; do printf "%-22s %s %s\n" "$u" "$(systemctl --user is-active $u.service 2>/dev/null)" "$(systemctl --user is-enabled $u.service 2>/dev/null)"; done; podman ps -a --format "{{.Names}} {{.Status}} nets=[{{.Networks}}]" | grep -Ei "hermes|signal|chrome"; ss -lntp 2>/dev/null | grep -wE "8080|8787|9119|9222" | tr -s " "'

If WebUI is up but Signal/Hermes transport errors appear:
1. Check signal-cli-daemon first:
   - ssh dankclaw 'systemctl --user status signal-cli-daemon.service --no-pager; journalctl --user -u signal-cli-daemon.service -n 120 --no-pager'
2. Only if appropriate, start/enable:
   - ssh dankclaw 'systemctl --user enable --now signal-cli-daemon.service'
3. Verify:
   - ssh dankclaw 'systemctl --user is-active signal-cli-daemon.service; ss -lntp | grep -w 8080'

Config edit caution:
- Do not replace /home/dank/hermes-data/config.yaml wholesale with repo example.
- Live /data/config.yaml ownership may require sudo-safe edit flow.
- After live config edits, restart the appropriate Hermes unit/container and verify health.

Model routing memory:
- Main model: frank-default-large via dankclaw-large at http://192.168.0.143:7770/v1.
- Vision auxiliary: gemma4-it:e4b at http://192.168.0.143:7771/v1 via provider/custom endpoint.