hermes-scheduler

name	hermes-scheduler
description	Background cron scheduler for recurring agent tasks. Start with /hermes-scheduler. Manages scheduled jobs that invoke Claude Code on cron/interval/one-shot schedules. Jobs persist across restarts. Inspired by NousResearch/hermes-agent scheduler. Use when scheduling recurring agent tasks on cron/interval/one-shot schedules.
version	1.0.0
author	jjohare
license	MIT
metadata	{"hermes":{"tags":["scheduler","cron","background","daemon","polling","always-on"],"category":"automation","related_skills":[]}}

Hermes Scheduler

Background cron scheduler that runs agent tasks on schedule. Jobs are defined in natural language, executed via Claude Code, and output saved per-run.

Commands

All commands run via the scheduler script at ~/.claude/skills/hermes-scheduler/scripts/scheduler.py.

# Start the scheduler daemon (background, 60-second tick)
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py start

# Stop the scheduler
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py stop

# Check status
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py status

# Create a job
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py add \
  --prompt "check disk usage and alert if over 80%" \
  --schedule "every 30m" \
  --name "disk-monitor"

# Create a one-shot job
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py add \
  --prompt "generate a weekly project status summary" \
  --schedule "30m"

# Create a cron job
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py add \
  --prompt "pull latest from all repos and run tests" \
  --schedule "0 9 * * *" \
  --name "morning-ci"

# List jobs
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py list

# Remove a job
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py remove --id <job_id>

# Pause / resume
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py pause --id <job_id>
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py resume --id <job_id>

# Trigger a job immediately
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py trigger --id <job_id>

# View recent output for a job
python3 ~/.claude/skills/hermes-scheduler/scripts/scheduler.py output --id <job_id>

Schedule Formats

Format	Type	Example
Duration	One-shot	30m, 2h, 1d
Interval	Recurring	every 30m, every 2h
Cron	Recurring	0 9 * * *, */15 * * * *
ISO timestamp	One-shot	2026-04-07T09:00

Job Execution

Each job runs as a subprocess: claude --print "<prompt>". The agent has full access to the workspace, tools, and MCP servers. Output is captured and saved to ~/.claude/scheduler/output/<job_id>/<timestamp>.md.

Persistence

• Jobs stored in ~/.claude/scheduler/jobs.json
• Output per-run in ~/.claude/scheduler/output/
• PID file at ~/.claude/scheduler/scheduler.pid
• Lock file prevents concurrent ticks
• At-most-once semantics: recurring jobs advance next_run_at BEFORE execution
• Stale job fast-forwarding: if the daemon was down and missed a window, skips to next future run

Architecture

Adapted from NousResearch/hermes-agent cron scheduler patterns. Standalone Python daemon with no Hermes dependencies. Integrates with Claude Code via subprocess invocation.