`openclaw cron`

Manage cron jobs for the Gateway scheduler.

Cron jobs: Cron jobs

Tip: run openclaw cron --help for the full command surface.

Note: isolated cron add jobs default to --announce delivery. Use --no-deliver to keep output internal. --deliver remains as a deprecated alias for --announce.

Note: one-shot (--at) jobs delete after success by default. Use --keep-after-run to keep them.

Note: --session supports main, isolated, current, and session:<id>. Use current to bind to the active session at creation time, or session:<id> for an explicit persistent session key.

Note: for one-shot CLI jobs, offset-less --at datetimes are treated as UTC unless you also pass --tz <iana>, which interprets that local wall-clock time in the given timezone.

Note: recurring jobs now use exponential retry backoff after consecutive errors (30s → 1m → 5m → 15m → 60m), then return to normal schedule after the next successful run.

Note: openclaw cron run now returns as soon as the manual run is queued for execution. Successful responses include { ok: true, enqueued: true, runId }; use openclaw cron runs --id <job-id> to follow the eventual outcome.

Note: openclaw cron run <job-id> force-runs by default. Use --due to keep the older "only run if due" behavior.

Note: retention/pruning is controlled in config:

cron.sessionRetention (default 24h) prunes completed isolated run sessions.
cron.runLog.maxBytes + cron.runLog.keepLines prune ~/.openclaw/cron/runs/<jobId>.jsonl.

Upgrade note: if you have older cron jobs from before the current delivery/store format, run openclaw doctor --fix. Doctor now normalizes legacy cron fields (jobId, schedule.cron, top-level delivery fields including legacy threadId, payload provider delivery aliases) and migrates simple notify: true webhook fallback jobs to explicit webhook delivery when cron.webhook is configured.

Common edits

Update delivery settings without changing the message:

openclaw cron edit <job-id> --announce --channel telegram --to "123456789"

Disable delivery for an isolated job:

openclaw cron edit <job-id> --no-deliver

Enable lightweight bootstrap context for an isolated job:

openclaw cron edit <job-id> --light-context

Announce to a specific channel:

openclaw cron edit <job-id> --announce --channel slack --to "channel:C1234567890"

Create an isolated job with lightweight bootstrap context:

openclaw cron add \
  --name "Lightweight morning brief" \
  --cron "0 7 * * *" \
  --session isolated \
  --message "Summarize overnight updates." \
  --light-context \
  --no-deliver

--light-context applies to isolated agent-turn jobs only. For cron runs, lightweight mode keeps bootstrap context empty instead of injecting the full workspace bootstrap set.

Common admin commands

Manual run:

openclaw cron run <job-id>
openclaw cron run <job-id> --due
openclaw cron runs --id <job-id> --limit 50

Agent/session retargeting:

openclaw cron edit <job-id> --agent ops
openclaw cron edit <job-id> --clear-agent
openclaw cron edit <job-id> --session current
openclaw cron edit <job-id> --session "session:daily-brief"

Delivery tweaks:

openclaw cron edit <job-id> --announce --channel slack --to "channel:C1234567890"
openclaw cron edit <job-id> --best-effort-deliver
openclaw cron edit <job-id> --no-best-effort-deliver
openclaw cron edit <job-id> --no-deliver

3.7 KiB Raw Blame History Unescape Escape

openclaw cron

Common edits

Common admin commands

3.7 KiB

Raw Blame History

`openclaw cron`