Script-Only Cron Jobs (No LLM)
Script Only Cron Jobs Sometimes you already know exactly what message you want to send. You don't need an agent to reason about it — you just need a script to r
- Section
- Guides & Tutorials
- Source
- hermesbible.com/docs/guides/cron-script-only
Script Only Cron Jobs Sometimes you already know exactly what message you want to send. You don't need an agent to reason about it — you just need a script to r
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- When to Use It
- Create One from Chat
- Example transcript
- What the agent decides for you
- Managing watchdogs from chat
- Create One from the CLI
- How Script Output Maps to Delivery
- Script Rules
- Schedule Syntax
- Delivery Targets
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
- When to Use It
- Create One from Chat
- Example transcript
- What the agent decides for you
- Managing watchdogs from chat
- Create One from the CLI
- How Script Output Maps to Delivery
- Script Rules
- Schedule Syntax
- Delivery Targets
- Editing and Lifecycle
- Worked Example: Disk Space Alert
- Comparison with Other Patterns
- Related
Section map
When to Use It
Maps when to use it to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Create One from Chat
Maps create one from chat to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Example transcript
Maps example transcript to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
What the agent decides for you
Maps what the agent decides for you to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Managing watchdogs from chat
Maps managing watchdogs from chat to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Create One from the CLI
Maps create one from the cli to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
How Script Output Maps to Delivery
Maps how script output maps to delivery to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Script Rules
Maps script rules to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: When to Use It, Create One from Chat, Example transcript, What the agent decides for you, Managing watchdogs from chat. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: script-only, script, sometimes, already, exactly. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for script-only cron jobs (no llm) before applying exact upstream commands.
Open the source anchor for When to Use It and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
- Start with the source section for When to Use It; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Create One from Chat if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
Set provider, token, and retry limits before scaling the workflow beyond a single test run.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page