hermes-agent-deploymentlisted

# Hermes Agent deployment Built and verified end-to-end 2026-08-31 deploying a personal instance on a Vultr VPS (`hermes-agent`, Dallas, Debian 13), wired to Telegram, LunaRoute (custom LLM provider), and Groq (voice transcription) — Will's nickname for the running instance is "Chuka" (a personal name, not an infra rename; every host/user/vault stays `hermes-*`). Every gotcha below was hit for real building it and its follow-on capabilities, not assumed from docs. Deliberately kept separate from the `homelab-ansible`-managed fleet (Will's call) but, per his standing Ansible-first instruction for this project, fully Ansible-managed from day one via its own `hermes-ansible` repo run **locally on the box** (`ansible_connection=local`), mirroring how `dfw-ansible` runs locally for OpenClaw rather than being pushed from `ansible-ctrl`. ## Install ```bash npm install -g @nousresearch/hermes-agent # exact package name — verify against current docs, # this is a fast-moving research-preview tool hermes --version ``` Run as a dedicated non-root `hermes` system user — Hermes's own installer refuses `--system` install as root without an override, since running a Telegram-driven exec-capable process as root indefinitely is a real risk, same reasoning as OpenClaw's `openclaw` user. Gateway service install is a CLI subcommand, not a hand-written unit file: ```bash hermes gateway install --system --run-as-user hermes --start-now --start-on