hermes

You operate a Hermes agent gateway already deployed by bento. Hermes runs gateway run and supervises, in parallel: an OpenAI-compatible API server (:8642, for bots/scripts), a dashboard (:9119, Traefik basic-auth gate), and a CLI reachable via docker exec. This is day-2 work — chat, configure, and extend the agent. You do NOT redeploy the stack — that is /bento:deploy. All artifacts stay in English.

Where config lives. The daemon's mutable config is /opt/data/config.yaml inside the hermes container (the .env next to it holds secrets, mode 0600). Edit config and add MCP servers in the hermes daemon container (hermes_hermes), never in another stack that mounts the binary read-only.

When to invoke

• "chat with / call my hermes agent" (from a script, bot, or by hand)
• "add an MCP server to hermes" / "give the agent the <youtube/search/...> tools"
• "list / inspect sessions", "list / enable / disable tools"
• "change the model or provider", "show the hermes config"

For getting hermes running use /bento:deploy. For provider API keys (OpenAI/Anthropic/OpenRouter) use /bento:auth — hermes reads those propagated envs.

Discover the instance — don't hardcode

ssh "$user@$host" "jq -r '.envs.hermes.HERMES_API_HOST' \$HOME/.config/bento/state.json"  # API gateway host
ssh "$user@$host" "jq -r '.envs.hermes.HERMES_HOST'     \$HOME/.config/bento/state.json"  # dashboard host
ssh "$user@$host" "jq -r '.envs.hermes.HERMES_API_KEY'  \$HOME/.config/bento/state.json"  # Bearer for the API (don't echo)
ssh "$user@$host" "jq -r '.envs.hermes.HERMES_MODEL_NAME' \$HOME/.config/bento/state.json" # advertised model name

API base URL = https://<HERMES_API_HOST>. Container (conventional in bento swarm): hermes_hermes.1.*.

hermes_container() { ssh "$user@$host" "docker ps --filter name=hermes_hermes -q | head -1"; }
hx() { ssh "$user@$host" "docker exec \$(docker ps -qf name=hermes_hermes) hermes $*"; }  # run a hermes CLI subcommand