Finding
Recurring Hermes checks are valuable, but they become brittle when cron jobs are created as one-off reminders instead of self-contained operational monitors with clear scope, delivery rules, and verification.
Current
A real Hermes installation often starts with a few useful scheduled jobs for model checks, optimizer review, dashboard review, feed monitoring, or maintenance reminders. The weak point is usually not the existence of cron jobs; it is that prompts can be vague, tool access can be broader than needed, and outputs can either disappear into local-only delivery or become noisy notifications. Without a small review habit, old cron jobs can keep running after their purpose changes.
Suggested
- Standardize every recurring job as an operational monitor, not a reminder. Exact change: add a “Cron job standard” section to
SOUL.mdor an internal runbook requiring each cron prompt to include purpose, sources to inspect, change criteria, allowed side effects, delivery target, and expected silence/noise behavior. - Restrict cron jobs to the minimum toolsets they need. Exact change: update each cron prompt or cron definition so routine checks declare only the relevant toolsets, such as
webfor public release checks,session_searchfor pattern review,cronjobfor cron audit, orfileonly when a local artifact must be read. - Add a weekly cron hygiene review. Exact change: create or update an Optimizer Agent cron prompt named “Cron hygiene review” that lists active jobs, flags jobs with vague prompts, excessive tool access, stale schedules, missing delivery intent, or unclear verification, and returns only actionable findings.
Impact
This turns scheduled autonomy into a controlled operating layer instead of a pile of background reminders. Hermes gains proactive drift detection, recurring research, and maintenance checks while reducing notification noise and token waste. Clear prompts and minimal toolsets also make cron behavior safer to expose in public maturity documentation without revealing private internals.
Effort
Small — the main work is a cron prompt rewrite, one operating rule in a runbook or SOUL.md, and a recurring review habit rather than a new system.
Public page note
Safe public content should describe the maturity pattern: use Hermes cron for recurring checks, write self-contained prompts, restrict toolsets, define delivery behavior, and review jobs for drift. Internal-only content must stay out of the page, including real cron IDs, private chat summaries, raw job outputs, local file paths with sensitive context, credentials, env values, and any live operational controls.