Hermes Cron
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.
Decision map
| Question |
Load |
| Every subcommand and flag |
cron-cli.md |
| Schedule syntax, timezone, where output goes |
schedules-delivery.md |
| Preflight, catch-up, cancel, alerts, doctor |
reliability.md |
| Daily / weekly / monthly job recipes |
templates/cron-jobs.md |
cron: config block |
templates/cron-config.yaml |
Critical rules
- Always pass
--workdir <absolute dir> for jobs that must follow
workspace rules. Without it a job runs detached: no .hermes.md,
AGENTS.md or CLAUDE.md is loaded and tools run from the gateway's
directory. The directory must exist and be absolute.
- SOUL.md still applies (it comes from the profile home), but put job
procedures in the prompt or
.hermes.md, not in SOUL.md.
- The scheduler lives in the gateway. No running gateway = no fires.
Check
hermes cron status after any change.
- Pin what must not drift. Unpinned jobs follow
cron.model, then the
main model at fire time. Use --pin or --model/--provider for jobs
whose output must stay stable; --reasoning-effort per job.
- Set the timezone. Expressions use the profile
timezone: unless
--timezone is given; an invalid zone silently means server time
(hermes doctor reports it).
- Stale briefs are useless: use
--catch-up off for time-bound reports.
- Deliver, don't send. The final response goes to
--deliver; cron
sessions cannot create cron jobs and must not be told to message people.
- Canary first:
--paused, then hermes cron run <job>, then resume.
Minimal job
hermes cron create "0 8 * * 1-5" "<PROMPT>" \
--name "<job-name>" \
--workdir "<ABSOLUTE_WORKSPACE_PATH>" \
--timezone "<Area/City>" \
--deliver "<TARGET>" \
--catch-up off \
--paused --paused-reason "canary"
hermes cron list # note the job id
hermes cron run <job-name> # manual run on the next scheduler tick (works while paused)
hermes cron runs <job_id> --limit 5
hermes cron resume <job-name>
Sources
1---2name: hermes-cron-23description: Use when scheduling Hermes Agent work - hermes cron create/edit/list/pause/resume/run/cancel/remove, schedule formats, --workdir (so .hermes.md loads), --timezone, --reasoning-effort, --catch-up, --grace-minutes, model pinning, delivery targets, preflight (blocked_config), failure alerts, daily/weekly/monthly job recipes. Not for what the jobs should say (hermes-rhythm), subagent limits (hermes-delegation) or messaging adapter setup (hermes-gateways).4metadata:5 source: https://skillmd.com/skills/fusengine/hermes-cron-26---78<objective>9Create and operate scheduled jobs in Hermes Agent 0.23.0 with `hermes cron`10(or `/cron` in chat, or the agent's `cronjob_manage` tool): schedule syntax,11per-job working directory, timezone, reasoning effort, model pin, missed-run12policy, delivery targets, preflight validation, cancellation and health13checks, plus generic daily/weekly/monthly recipes. Every flag here was read in14the official cron docs or the v0.23.0 release notes.15</objective>1617# Hermes Cron1819## Freshness check2021Before writing or changing any Hermes config, run `hermes --version` and22`hermes update --check`, then read23https://github.com/NousResearch/hermes-agent/releases/latest. If the installed24or latest version is newer than 0.23.0, read every release note since 0.23.025("Upgrade notes" first) and adjust. Never apply guidance from this skill to a26newer version without that check.2728## Decision map2930| Question | Load |31|----------|------|32| Every subcommand and flag | [cron-cli.md](references/cron-cli.md) |33| Schedule syntax, timezone, where output goes | [schedules-delivery.md](references/schedules-delivery.md) |34| Preflight, catch-up, cancel, alerts, doctor | [reliability.md](references/reliability.md) |35| Daily / weekly / monthly job recipes | [templates/cron-jobs.md](references/templates/cron-jobs.md) |36| `cron:` config block | [templates/cron-config.yaml](references/templates/cron-config.yaml) |3738## Critical rules39401. **Always pass `--workdir <absolute dir>`** for jobs that must follow41 workspace rules. Without it a job runs detached: no `.hermes.md`,42 `AGENTS.md` or `CLAUDE.md` is loaded and tools run from the gateway's43 directory. The directory must exist and be absolute.442. **SOUL.md still applies** (it comes from the profile home), but put job45 procedures in the prompt or `.hermes.md`, not in SOUL.md.463. **The scheduler lives in the gateway.** No running gateway = no fires.47 Check `hermes cron status` after any change.484. **Pin what must not drift.** Unpinned jobs follow `cron.model`, then the49 main model at fire time. Use `--pin` or `--model/--provider` for jobs50 whose output must stay stable; `--reasoning-effort` per job.515. **Set the timezone.** Expressions use the profile `timezone:` unless52 `--timezone` is given; an invalid zone silently means server time53 (`hermes doctor` reports it).546. **Stale briefs are useless:** use `--catch-up off` for time-bound reports.557. **Deliver, don't send.** The final response goes to `--deliver`; cron56 sessions cannot create cron jobs and must not be told to message people.578. **Canary first:** `--paused`, then `hermes cron run <job>`, then resume.5859## Minimal job6061```bash62hermes cron create "0 8 * * 1-5" "<PROMPT>" \63 --name "<job-name>" \64 --workdir "<ABSOLUTE_WORKSPACE_PATH>" \65 --timezone "<Area/City>" \66 --deliver "<TARGET>" \67 --catch-up off \68 --paused --paused-reason "canary"69hermes cron list # note the job id70hermes cron run <job-name> # manual run on the next scheduler tick (works while paused)71hermes cron runs <job_id> --limit 572hermes cron resume <job-name>73```7475## Sources7677- https://hermes-agent.nousresearch.com/docs/user-guide/features/cron78- https://hermes-agent.nousresearch.com/docs/reference/cli-commands (`hermes cron`)79- https://hermes-agent.nousresearch.com/docs/user-guide/configuration (timezone)80- https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.0 (cancel, --catch-up)