Cron Management

Cron Management

Crons are daemon-managed. They are stored in ${CTX_ROOT}/state/$CTX_AGENT_NAME/crons.json and dispatched by the cortextOS daemon. Crons survive agent restarts, context compactions, and daemon restarts automatically. You do NOT need to recreate them on session start.

Never use /loop or CronCreate for persistent recurring work — those are session-local and die on agent restart.

On Session Start

Check that your crons are registered. Do not recreate them unless they are missing.

cortextos bus list-crons $CTX_AGENT_NAME

If a cron is missing from the list, add it:

cortextos bus add-cron $CTX_AGENT_NAME <name> <interval|cron-expr> "<prompt>"

Adding a Recurring Cron

Interval shorthand (s/m/h/d/w):

cortextos bus add-cron $CTX_AGENT_NAME heartbeat 6h "Read HEARTBEAT.md and follow its instructions."
cortextos bus add-cron $CTX_AGENT_NAME health-check 30m "Check system health and report anomalies."

5-field cron expression (minute hour dom month dow):

cortextos bus add-cron $CTX_AGENT_NAME morning-report "0 9 * * 1-5" "Generate and send the daily analytics report."
cortextos bus add-cron $CTX_AGENT_NAME weekly-summary "0 17 * * 5" "Compile and deliver the weekly summary."

The daemon reloads automatically after add-cron. Confirm with list-crons.

Updating a Cron

# Change the schedule
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --interval 4h

# Update the prompt
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --prompt "New prompt text."

# Disable (stops firing without removing it)
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --enabled false

# Re-enable
cortextos bus update-cron $CTX_AGENT_NAME heartbeat --enabled true

Removing a Cron

cortextos bus remove-cron $CTX_AGENT_NAME <name>

Testing a Cron Immediately

From the dashboard (/workflows/$CTX_AGENT_NAME/<name>), click Test Fire to inject the cron's prompt immediately. A 30-second cooldown prevents accidental rapid-fires.

Set manualFireDisabled: true on a cron definition to block dashboard test-fires (e.g. for crons that must only fire on schedule).

Checking Execution History

# All crons for this agent
cortextos bus get-cron-log $CTX_AGENT_NAME

# Filter to a specific cron
cortextos bus get-cron-log $CTX_AGENT_NAME <name>

Each log entry: ts, cron, status (fired/retried/failed), attempt, duration_ms, error.

Troubleshooting

Cron not firing:

1. cortextos bus list-crons $CTX_AGENT_NAME — confirm it is registered and not disabled.
2. cortextos bus get-cron-log $CTX_AGENT_NAME <name> — check for status: failed entries.
3. Check daemon log: ~/.cortextos/$CTX_INSTANCE_ID/logs/$CTX_AGENT_NAME/

crons.json corrupted:

• readCrons automatically falls back to crons.json.bak on parse failure. Usually self-healing.
• If both files are bad, re-add crons via add-cron or force re-migration: cortextos bus migrate-crons $CTX_AGENT_NAME --force

Scheduler retained stale schedule after reload:

• If a reload produces an empty schedule (transient corruption), the daemon keeps the last-good schedule in memory (lastGoodSchedule). Crons keep firing. Repair crons.json and the scheduler recovers automatically on the next reload.