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-cron3description: 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).4versions:5 hermes-agent: "0.23.0"6user-invocable: false7references:8 - references/cron-cli.md9 - references/schedules-delivery.md10 - references/reliability.md11 - references/templates/cron-jobs.md12 - references/templates/cron-config.yaml13related-skills:14 - hermes-core15 - hermes-delegation16 - hermes-gateways17 - hermes-rhythm18 - hermes-security19metadata:20 source: https://skillmd.com/skills/fusengine/hermes-cron21---2223<objective>24Create and operate scheduled jobs in Hermes Agent 0.23.0 with `hermes cron`25(or `/cron` in chat, or the agent's `cronjob_manage` tool): schedule syntax,26per-job working directory, timezone, reasoning effort, model pin, missed-run27policy, delivery targets, preflight validation, cancellation and health28checks, plus generic daily/weekly/monthly recipes. Every flag here was read in29the official cron docs or the v0.23.0 release notes.30</objective>3132# Hermes Cron3334## Freshness check3536Before writing or changing any Hermes config, run `hermes --version` and37`hermes update --check`, then read38https://github.com/NousResearch/hermes-agent/releases/latest. If the installed39or latest version is newer than 0.23.0, read every release note since 0.23.040("Upgrade notes" first) and adjust. Never apply guidance from this skill to a41newer version without that check.4243## Decision map4445| Question | Load |46|----------|------|47| Every subcommand and flag | [cron-cli.md](references/cron-cli.md) |48| Schedule syntax, timezone, where output goes | [schedules-delivery.md](references/schedules-delivery.md) |49| Preflight, catch-up, cancel, alerts, doctor | [reliability.md](references/reliability.md) |50| Daily / weekly / monthly job recipes | [templates/cron-jobs.md](references/templates/cron-jobs.md) |51| `cron:` config block | [templates/cron-config.yaml](references/templates/cron-config.yaml) |5253## Critical rules54551. **Always pass `--workdir <absolute dir>`** for jobs that must follow56 workspace rules. Without it a job runs detached: no `.hermes.md`,57 `AGENTS.md` or `CLAUDE.md` is loaded and tools run from the gateway's58 directory. The directory must exist and be absolute.592. **SOUL.md still applies** (it comes from the profile home), but put job60 procedures in the prompt or `.hermes.md`, not in SOUL.md.613. **The scheduler lives in the gateway.** No running gateway = no fires.62 Check `hermes cron status` after any change.634. **Pin what must not drift.** Unpinned jobs follow `cron.model`, then the64 main model at fire time. Use `--pin` or `--model/--provider` for jobs65 whose output must stay stable; `--reasoning-effort` per job.665. **Set the timezone.** Expressions use the profile `timezone:` unless67 `--timezone` is given; an invalid zone silently means server time68 (`hermes doctor` reports it).696. **Stale briefs are useless:** use `--catch-up off` for time-bound reports.707. **Deliver, don't send.** The final response goes to `--deliver`; cron71 sessions cannot create cron jobs and must not be told to message people.728. **Canary first:** `--paused`, then `hermes cron run <job>`, then resume.7374## Minimal job7576```bash77hermes cron create "0 8 * * 1-5" "<PROMPT>" \78 --name "<job-name>" \79 --workdir "<ABSOLUTE_WORKSPACE_PATH>" \80 --timezone "<Area/City>" \81 --deliver "<TARGET>" \82 --catch-up off \83 --paused --paused-reason "canary"84hermes cron list # note the job id85hermes cron run <job-name> # manual run on the next scheduler tick (works while paused)86hermes cron runs <job_id> --limit 587hermes cron resume <job-name>88```8990## Sources9192- https://hermes-agent.nousresearch.com/docs/user-guide/features/cron93- https://hermes-agent.nousresearch.com/docs/reference/cli-commands (`hermes cron`)94- https://hermes-agent.nousresearch.com/docs/user-guide/configuration (timezone)95- https://github.com/NousResearch/hermes-agent/releases/tag/v0.23.0 (cancel, --catch-up)