local-scheduler

Local Scheduler

Set up a Claude Code command to run automatically on your own machine, via launchd on Mac or Task Scheduler on Windows. Runs locally, so it has access to your filesystem, shell env, and local MCP servers — unlike native /schedule, which runs remote agents in the cloud.

Use this when the scheduled command needs:

• Local files (reading/writing your vault)
• Local tools (launchd, rclone, gcloud, etc.)
• Shell env vars (API tokens in ~/.zshrc)
• A specific working directory

For anything that can run in the cloud, use the native /schedule command instead.

Step 0: Detect OS

uname -s 2>/dev/null || echo "Windows"

If the output contains "MINGW", "CYGWIN", "MSYS", or "Windows", this is Windows. Use PowerShell and Task Scheduler. Otherwise, use bash and launchd.

Step 1: What to Schedule

Use AskUserQuestion:

"What do you want to run on a schedule?"

Offer common options plus a custom option:

• "/morning — morning brief"
• "/delegate — process delegation queue"
• "/voice-router — route voice notes"
• "Custom command"

If they pick custom, ask what command or prompt to run.

Step 2: When to Run

Use AskUserQuestion:

"How often should it run?"

Options:

• "Daily (pick a time)"
• "Multiple times a day (pick times)"
• "Weekly (pick a day and time)"
• "Every N hours"

Then ask for the specific time(s). Default suggestions:

• Morning brief: daily at 8:30am
• Delegate: daily at 9am
• Voice router: every 2 hours, 8am-10pm

Step 3: Check for Conflicts

# macOS
ls ~/Library/LaunchAgents/com.claude.* 2>/dev/null | xargs -I {} basename {} .plist | sed 's/com.claude.//'

# Windows
powershell.exe -Command "Get-ScheduledTask | Where-Object {$_.TaskName -like 'Claude*'} | Format-Table TaskName,State" 2>/dev/null

If the same command is already scheduled, tell the user and ask if they want to replace it.

Step 4: Create the Runner Script

Find the claude path:

which claude

macOS/Linux

Create ops/scripts/scheduled/TASKNAME.sh: