KrustyPlanet/hermes-agent
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs(cron): document CronScheduler provider + cron.provider key

Browse source 
Phase 3.5. cron-internals.md gateway-integration section now describes the
pluggable trigger (resolve_cron_scheduler, built-in default, plugins/cron
discovery, the never-without-a-trigger fallback, and the trigger-vs-execution
split). cli-commands.md notes cron.provider near the hermes cron entry.
This commit is contained in:
Ben 2026-06-18 14:18:31 +10:00
parent abbd8646eb
commit bfb6e0bb33
2 changed files with 31 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
website/docs/reference/cli-commands.md
View file

@ -533,6 +533,13 @@ hermes cron <list|create|edit|pause|resume|run|remove|status|tick>
| `status` | Check whether the cron scheduler is running. |
| `tick` | Run due jobs once and exit. |
The cron **trigger** is pluggable via the `cron.provider` config key. Empty
(the default) uses the built-in in-process ticker. A named provider (e.g.
`chronos`, a managed-cron provider for scale-to-zero deployments) is discovered
from `plugins/cron/<name>/` or `$HERMES_HOME/plugins/<name>/`; an unknown or
unavailable provider falls back to the built-in, so cron is never left without
a trigger. See the [cron internals](../developer-guide/cron-internals.md#gateway-integration) doc.
## `hermes kanban`
```bash