1.6 KiB
1.6 KiB
Cron Job Model Fix (Post-Update)
Session: 2026-05-08 | Impact: All cron jobs with model: null break after Hermes Agent update
Problem
After a Hermes Agent update, cron jobs with model: null fail immediately:
Error code: 400 - {'message': 'model should be in provider/model format'}
The new codepath strictly validates the model field — it no longer auto-resolves from config.
Fix Pattern
Step 1: Identify affected jobs
hermes cron list
Look for jobs where model: null.
Step 2: Apply explicit model
hermes cron update <job-id> --model '{"model": "<provider>/<model>"}'
Example for this setup:
hermes cron update <job-id> --model '{"model": "custom/llama/model.gguf"}'
Step 3: Verify
hermes cron list --name <job-name>
Confirm model is now custom/llama/model.gguf.
Step 4: Restart gateway (if running)
systemctl --user restart hermes-gateway
The gateway process caches job definitions in memory. Restart ensures it loads updated models.
Prevention
When creating new cron jobs, always specify the model explicitly:
hermes cron create --name "..." --model '{"model": "custom/llama/model.gguf"}' --prompt "..."
Or for script-only jobs (no LLM needed), set --no-agent:
hermes cron create --name "..." --script "..." --no-agent
Session-Specifics (2026-05-08)
Three jobs were affected by the update to v0.13.0 (commit 474d1e812):
SRE Network Reconnaissance(4733a436d99a) → fixedRechnungen-Organizer(f773f8c23230) → fixedmemory-sync-daily(ce496a8d1062) → deleted and recreated asno_agent: truescript-only