Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Scheduled Tasks (Cron)

Schedule tasks to run automatically with natural language or cron expressions. Hermes exposes cron management through a single tool with action style operations

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/cron

Schedule tasks to run automatically with natural language or cron expressions. Hermes exposes cron management through a single tool with action style operations

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. What cron can do now
  2. Creating scheduled tasks
  3. In chat with /cron
  4. From the standalone CLI
  5. Through natural conversation
  6. Skill-backed cron jobs
  7. Single skill
  8. Multiple skills
  9. Running a job inside a project directory
  10. Editing jobs
  11. Chat
  12. Standalone CLI
  13. Lifecycle actions
  14. Chat

Section map

What cron can do now

Maps what cron can do now to the Core Features documentation path, with the source page reserved for exact commands and updates.

Creating scheduled tasks

Maps creating scheduled tasks to the Core Features documentation path, with the source page reserved for exact commands and updates.

In chat with /cron

Maps in chat with /cron to the Core Features documentation path, with the source page reserved for exact commands and updates.

From the standalone CLI

Maps from the standalone cli to the Core Features documentation path, with the source page reserved for exact commands and updates.

Through natural conversation

Maps through natural conversation to the Core Features documentation path, with the source page reserved for exact commands and updates.

Skill-backed cron jobs

Maps skill-backed cron jobs to the Core Features documentation path, with the source page reserved for exact commands and updates.

Single skill

Maps single skill to the Core Features documentation path, with the source page reserved for exact commands and updates.

Multiple skills

Maps multiple skills to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features 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: What cron can do now, Creating scheduled tasks, In chat with /cron, From the standalone CLI, Through natural conversation. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: scheduled, tasks, schedule, automatically, natural. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for scheduled tasks (cron) before applying exact upstream commands.

Verify firstWhat cron can do now

Open the source anchor for What cron can do now and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for What cron can do now; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Creating scheduled tasks if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

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