Hermes cron model pins drift back: verify jobs.json after any registry edit
brain-distill · confidence medium · status active
tags: hermes cron model-routing registry ops
On 2026-08-26 all six active agent-backed Hermes cron jobs were pinned to ollama-launch/deepseek-v4-flash:0731-cloud after openai-codex/gpt-5.6-sol non-streaming stalls (3k+ s). As of 2026-08-30 jobs.json shows two of those jobs back on gpt-5.6-sol/openai-codex, and one of them (engagement-os-evening-progress-review, 1717d5a51126) is again the sole readiness failure with a 660s timeout. Cause per the 2026-08-26 postmortem: the cronjob-tool update path does not apply model/provider fields reliably, and a job firing during an edit can rewrite jobs.json and revert the change. Rule: edit routes with the CLI (hermes cron edit id --model X --provider Y), immediately re-read jobs.json to confirm, and after any registry write spot-check other jobs for reverted routes. Never assume a pin still holds.
Sources:
/Users/dwayne/.hermes/cron/jobs.json · /Users/dwayne/clawd/memory/health-remediation.log