Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Daily Use

19. Daily Use — Running Hermes in Your Daily Rhythm

If the previous chapters were about building infrastructure, configuration, and security, this one is about the daily experience of living with an agent — texting from your phone, picking up a conversation that was left half-finished, correcting course mid-task while the agent is working, or trusting it enough to let it do sensitive things on its own. The common thread through all seven sub-sections: Hermes is designed to be continuous, not a disconnected chat session every time you open it.

The big picture

Exactly as the official README describes it: a single gateway process serves Telegram, Discord, Slack, WhatsApp, Signal, and the CLI at the same time — with cross-platform conversation continuity. The seven sub-sections below are seven concrete facets of “living with” an agent like that:

  1. Texting from your phone (19.1) when you are not at your computer.
  2. Work continues while your PC is off (19.2), thanks to the always-on VPS architecture.
  3. Picking up exactly where you left off (19.3), no matter how much time has passed.
  4. Separating multiple agent “personalities” for different purposes (19.4).
  5. Correcting course right in the middle of the agent’s work (19.5).
  6. Results arriving where they need to arrive (19.6) — no mixing up channels.
  7. Stopping to ask before sensitive actions (19.7) — the final boundary of trust.