mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-04-25 00:51:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs(cron): explain runtime resolution for null model/provider

Browse source 
Clarify job storage behavior regarding model and provider fields.
This commit is contained in:
wenhao7 2026-04-07 16:54:52 +08:00 • committed by Teknium
parent fa47cbd456
commit 156b358320
1 changed files with 2 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
website/docs/user-guide/features/cron.md
View file

@ -338,6 +338,8 @@ For `update`, pass `skills=[]` to remove all attached skills.
Jobs are stored in `~/.hermes/cron/jobs.json`. Output from job runs is saved to `~/.hermes/cron/output/{job_id}/{timestamp}.md`. Jobs are stored in `~/.hermes/cron/jobs.json`. Output from job runs is saved to `~/.hermes/cron/output/{job_id}/{timestamp}.md`.
Jobs may store `model` and `provider` as `null`. When those fields are omitted, Hermes resolves them at execution time from the global configuration. They only appear in the job record when a per-job override is set.
The storage uses atomic file writes so interrupted writes do not leave a partially written job file behind. The storage uses atomic file writes so interrupted writes do not leave a partially written job file behind.
## Self-contained prompts still matter ## Self-contained prompts still matter