Day 4 , Automation, Delegation & Scheduling

There is a specific moment in every growing Hermes setup where you realize you are the scheduler. You remember to run the morning report. You kick off the parallel tasks by hand. You copy the webhook payload out of an email and paste it into a terminal. Day 4 is about handing those jobs to Hermes so it runs them whether you are at the keyboard or not.

By the end of today Hermes will be running on its own clock, delegating work to subagents, spawning parallel workers in separate terminal sessions, responding to external events through webhooks, and keeping separate projects walled off in their own profiles with independent models, skills, and cron tables.

What you will have by the end of today

• Cron jobs that run reports, health checks, or data syncs on a schedule you define, with per-job model overrides and skill attachments
• Subagent delegation via delegate_task so one orchestrator agent can farm out independent work to child agents that run in parallel
• Multi-agent workflows spawned through tmux with one-shot mode, worktree isolation, and session resume
• Webhook subscriptions that trigger agent runs when an external system, GitHub, Linear, a monitoring service, sends an event
• Profiles that isolate different projects with their own models, skills, cron tables, and memories

Lessons

1. Cron Jobs, Scheduled Agent Runs , hermes cron commands, schedule syntax, model overrides, skill attachments, script mode, and context chaining
2. Subagent Delegation , the delegate_task tool: single, batch, and background delegation with orchestrator/leaf roles and concurrency controls
3. Multi-Agent Workflows , spawning agents in tmux sessions, one-shot mode, worktree isolation, and session resume for persistent parallel workers
4. Webhooks, Event-Driven Agent Runs , hermes webhook subscribe, payload templating, testing, and connecting external systems to Hermes
5. Profiles, Isolated Agent Contexts , creating, switching, cloning, and exporting profiles with independent configurations

The automation features build on each other. Cron jobs are the foundation, a scheduled trigger that fires at a known time. Delegation adds concurrency inside a single run. Multi-agent workflows make those parallel workers durable and independent. Webhooks let the outside world pull the trigger. And profiles keep it all clean when you have multiple projects that should never share a cron table or a memory file.

Next: Day 5 , Production, Security & Extension