hermes
| Version | 2026.144.1443 |
| Repo | superproject |
Hermes self-improving AI agent by Nous Research, installed as a pixi CLI with a supervised entrypoint
The hermes candy installs the upstream Nous Research hermes-agent as a
non-editable pip package into the pixi default environment, so the
hermes CLI lands at ${HOME}/.pixi/envs/default/bin/hermes. It also
stages the full hermes-agent source tree under $HOME (for the bundled
.env / config examples, skills, and the WhatsApp bridge) and copies an
executable hermes-entrypoint wrapper onto the user PATH. At deploy time
the entrypoint runs under supervisord, mounts the persistent /opt/data
volume, and one-time auto-configures an LLM provider from the supplied
API key. Every claim below is observable: the binary, the wrapper, and
the source tree are real files in the image, and the running service +
data volume are probed against a live deployment.
Services
Section titled “Services”hermeshermes-whatsapp
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
run |
mkdir=${HOME}/.local/bin |
run |
copy=hermes-entrypoint |
check |
the hermes Python CLI is installed into the pixi default environment |
check |
the hermes entrypoint wrapper is installed and executable on the user PATH |
check |
the upstream hermes-agent source tree is staged under $HOME so the entrypoint can bootstrap config, skills, and the WhatsApp bridge |
agent-check |
when deployed, the persistent /opt/data volume is mounted and the supervised hermes service reaches a running state, having auto-configured an LLM provider from the supplied API key |
check |
file=/opt/data |
check |
service=hermes |