From 156b3583206d20cf6ca4b3017151d7e9a1a041f3 Mon Sep 17 00:00:00 2001
From: wenhao7 <67779267+wenhao7@users.noreply.github.com>
Date: Tue, 7 Apr 2026 16:54:52 +0800
Subject: [PATCH] docs(cron): explain runtime resolution for null
 model/provider

Clarify job storage behavior regarding model and provider fields.
---
 website/docs/user-guide/features/cron.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/docs/user-guide/features/cron.md b/website/docs/user-guide/features/cron.md
index 4628fcc639..85269faadd 100644
--- a/website/docs/user-guide/features/cron.md
+++ b/website/docs/user-guide/features/cron.md
@@ -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 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.
 
 ## Self-contained prompts still matter