Hermes Rhythm
Freshness check
Before writing or changing any Hermes config, run hermes --version and
hermes update --check, then read
https://github.com/NousResearch/hermes-agent/releases/latest. If the installed
or latest version is newer than 0.23.0, read every release note since 0.23.0
("Upgrade notes" first) and adjust. Never apply guidance from this skill to a
newer version without that check.
The rhythm
| Ritual | Default schedule | Content | Delivered to |
|---|---|---|---|
| Morning brief | 0 8 * * * |
Urgent · Decisions waiting · Company · Private · Agenda (one-minute read) | Owner conversation |
| Pilot check | During the day, e.g. every 2h |
Chase blocked cards, deliver what is ready; silent if nothing | Decisions channel |
| Evening review | 0 18 * * * |
Done · Left · Waiting for the owner (no card list) | Owner conversation |
| Weekly review | 0 8 * * 1 |
Pipeline, invoices, projects, open private dossiers, goals of the week | Owner conversation |
| Monthly dashboard | 0 8 1 * * |
Invoiced, unpaid, payroll and charges, admin deadlines of the month | Owner conversation |
| Daily fresh context | Once a day | Conversation reset; state lives in files, not chat | - |
Details per ritual: rituals.md. Exact jobs: templates/cron-jobs.md.
What is native and what is a pattern
| Piece | Status | Where |
|---|---|---|
| Scheduled prompts with delivery to a platform/channel | Native (hermes cron) |
hermes-cron |
Silent run when nothing to report ([SILENT]) |
Native | hermes-cron |
Job loads .hermes.md rules |
Native only with --workdir |
hermes-cron |
| Commitments registry | Pattern, not built-in - a file or Kanban tasks read by every brief | commitments-registry.md |
| Decisions channel | Pattern on native delivery targets | decisions-and-reset.md |
| Daily conversation reset | Not native since v0.22.0 - catalog plugin hermes-session-reset-policy or /new |
decisions-and-reset.md, hermes-core |
Critical rules
- Every ritual reads files, not chat history. Registry, dossier READMEs and the board are the memory; the conversation can be reset daily.
--workdiron every ritual job so the workspace.hermes.mdloads (cron jobs run detached otherwise).- Stale briefs are useless - morning brief with
--catch-up off(the docs use this exact example). - Nothing new = silence, not "nothing to report" messages.
- Unanswered "Go?" items return in every brief until answered.
- A ritual job never sends externally; it reports to the owner. The
chief's
approvals.cron_modeisapprove; sending stays blocked byapprovals.denyand the go gate (hermes-security).
Sources
- https://hermes-agent.nousresearch.com/docs/user-guide/features/cron
- https://hermes-agent.nousresearch.com/docs/reference/cli-commands (
hermes cron) - https://hermes-agent.nousresearch.com/docs/user-guide/messaging/ (Session continuity)
- https://hermes-agent.nousresearch.com/docs/user-guide/features/kanban
- https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.0