Cron Config Files — How This Works

Cron Config Files — GitOps for OpenClaw

How to edit a cron from Obsidian

1. Open any .md file in this folder
2. Edit the schedule, enabled, timeout_seconds, or the Prompt section
3. Save → Obsidian Git auto-commits and pushes to GitHub
4. Within ~60 seconds, OpenClaw detects the push and applies your changes automatically

File format

Each file has:

• YAML frontmatter — machine config (cron_id, schedule, model, delivery, etc.)
• Markdown body — the prompt the agent receives when the cron fires

What you can safely edit

Field	What it does
enabled: true/false	Turn the cron on or off
schedule	Cron expression, e.g. 0 16 * * * = 4PM UTC daily
timezone	e.g. America/Los_Angeles
timeout_seconds	Max time the agent can run
model	Override model (leave blank = default)
The Prompt section body	What the agent is told to do

What NOT to edit

• cron_id — this links the file to a live cron in OpenClaw; never change it
• delivery_channel / delivery_mode — changing channel routing requires a rule change, not just a file edit

Timezone note

All schedule expressions use UTC unless timezone is set. For PST schedules:

• 4PM PST = 0 0 * * * (midnight UTC, Nov–Mar) — use timezone: America/Los_Angeles instead

Example edit

To change Nader’s email digest from 4PM to 5PM PST, open nader-email-digest.md and change:

schedule: "0 16 * * *"

to:

schedule: "0 17 * * *"

Save, let Obsidian Git push, and it’s live within a minute.