d578d06f59
CRITICAL fixes: - Installation: Remove false prerequisites (installer auto-installs everything except git) - Tools: Remove non-existent 'web_crawl' tool from tools table - Memory: Remove non-existent 'read' action (only add/replace/remove exist) - Code execution: Fix 'search' to 'search_files' in sandbox tools list - CLI commands: Fix --model/--provider/--toolsets/--verbose as chat subcommand flags IMPORTANT fixes: - Installation: Add missing installer features (Node.js, ripgrep, ffmpeg, skills seeding) - Installation: Add 6 missing package extras to table (mcp, honcho, tts-premium, etc) - Installation: Fix mkdir to include all directories the installer creates - Quickstart: Add OpenAI Codex to provider table - CLI: Fix all 'hermes --flag' to 'hermes chat --flag' across all docs - Configuration: Remove non-existent --max-turns CLI flag - Tools: Fix 'search' to 'search_files', add missing 'process' tool - Skills: Remove skills_categories() (not a registered tool) - Cron: Remove unsupported 'daily at 9am' schedule format - TTS: Fix output directory to ~/.hermes/audio_cache/ - Delegation: Clarify depth limit wording - Architecture: Fix default model, chat() signature, file names - Contributing: Fix Python requirement from 3.11+ to 3.10+ - CLI reference: Add missing commands (login, tools, sessions subcommands) - Env vars: Fix TERMINAL_DOCKER_IMAGE default, add HERMES_MODEL
2.4 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 5 | Scheduled Tasks (Cron) | Schedule automated tasks with natural language — cron jobs, delivery options, and the gateway scheduler |
Scheduled Tasks (Cron)
Schedule tasks to run automatically with natural language or cron expressions. The agent can self-schedule using the schedule_cronjob tool from any platform.
Creating Scheduled Tasks
In the CLI
Use the /cron slash command:
/cron add 30m "Remind me to check the build"
/cron add "every 2h" "Check server status"
/cron add "0 9 * * *" "Morning briefing"
/cron list
/cron remove <job_id>
Through Natural Conversation
Simply ask the agent on any platform:
Every morning at 9am, check Hacker News for AI news and send me a summary on Telegram.
The agent will use the schedule_cronjob tool to set it up.
How It Works
Cron execution is handled by the gateway daemon. The gateway ticks the scheduler every 60 seconds, running any due jobs in isolated agent sessions:
hermes gateway install # Install as system service (recommended)
hermes gateway # Or run in foreground
hermes cron list # View scheduled jobs
hermes cron status # Check if gateway is running
:::info Even if no messaging platforms are configured, the gateway stays running for cron. A file lock prevents duplicate execution if multiple processes overlap. :::
Delivery Options
When scheduling jobs, you specify where the output goes:
| Option | Description |
|---|---|
"origin" |
Back to where the job was created |
"local" |
Save to local files only |
"telegram" |
Telegram home channel |
"discord" |
Discord home channel |
"telegram:123456" |
Specific Telegram chat |
The agent knows your connected platforms and home channels — it'll choose sensible defaults.
Schedule Formats
- Relative:
30m,2h,1d - Interval:
"every 30m","every 2h" - Cron expressions:
"0 9 * * *"(standard 5-field cron syntax) - ISO timestamps:
"2026-03-15T09:00:00"(one-time scheduled execution)
Managing Jobs
# CLI commands
hermes cron list # View all scheduled jobs
hermes cron status # Check if the scheduler is running
# Slash commands (inside chat)
/cron list
/cron remove <job_id>
Security
:::warning Scheduled task prompts are scanned for instruction-override patterns (prompt injection). Jobs with suspicious content are blocked. :::