Gabriel Koerich Orchestrator

Define recurring work with cron expressions. Jobs create tasks on schedule (or run bash commands directly).

Commands

orch job add "0 9 * * *" "Daily report" "body" "labels"
orch job add --type bash --command "echo hello" "@hourly" "Ping"
orch job list
orch job enable <id>
orch job disable <id>
orch job remove <id>
orch job tick          # manually check and fire due jobs

Job Types

How It Works

1. Jobs are defined in ~/.orchestrator/jobs.yml
2. jobs_tick.sh runs every poll cycle (10s) and checks cron schedules
3. When a schedule matches, a task is created (or command is run)
4. Jobs skip if a previous task from the same job is still in-flight (active_task_id)
5. Job-created tasks get scheduled and job:{id} labels

Cron Expressions

Standard cron syntax with aliases:

┌───────── minute (0-59)
│ ┌─────── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌─── month (1-12)
│ │ │ │ ┌─ day of week (0-6, Sun=0)
│ │ │ │ │
* * * * *

Aliases: @hourly, @daily, @weekly, @monthly, @yearly

Example

# Run code quality check every morning
orch job add "0 9 * * 1-5" "Code quality review" "Run lints, check for TODO items, update docs"

# Database backup every night (bash, no agent)
orch job add --type bash --command "pg_dump mydb > /backups/nightly.sql" "0 2 * * *" "DB backup"

Jobs integrate with GitHub sync — job-created tasks get synced to GitHub issues like any other task.