Add automation only after the baseline works
Turn a verified conversation into a repeatable task while keeping scope, permissions, and recovery visible.
Automation is a second layer
Hermes documentation groups cron scheduling, batch processing, delegation, and hooks under task automation. Each one increases leverage—and increases the cost of a mistaken instruction. Treat the first successful chat as a prerequisite, not as proof that a recurring job is safe.
Define the job before scheduling it
- What exact input does the job read?
- What is the narrowest output it should produce?
- Which tools and files are necessary?
- Where should failure be reported?
- How can the job be stopped or replayed safely?
Write the answers in the task prompt or an accompanying runbook. A future reader should not have to infer the boundaries from a vague instruction.
Start with a dry run
Run the task manually with a small fixture or read-only scope. Review the output, then schedule it at a low-risk cadence. Keep the first automation observable: record the source revision, the time, the result, and any files changed.
Primary sources for this lesson: Hermes Quickstart · Hermes Learning Path