openclaw-add-cron

Creates scheduled cron, every, or at jobs in OpenClaw with isolated sessions and stow deployment.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-add-cron-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-add-cron
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/openclaw-skills/skills/openclaw-add-cron
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-add-cron-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding scheduled jobs to OpenClaw can break the symlinked cron state or leak context between runs. This Skill provides a validated, repeatable procedure for registering cron, every, or at jobs in openclaw.json while protecting the transient jobs.json state and gateway deployment. ## Core Features & Use Cases - Validated Job Registration: Enforces required inputs (job_id, agent_id, schedule_type, schedule_value, prompt) and rejects invalid schedule types before writing config. - Isolated Execution by Default: Jobs run in isolated sessions to prevent context bleed and control token cost across scheduled tasks. - Safe Deployment Workflow: Removes the transient ~/.openclaw/cron/jobs.json, deploys with stow, restarts the gateway via launchctl, and verifies job materialization and scheduler logs. - Use Case: Schedule a recurring nightly memory-maintenance agent job by adding it to openclaw.json, redeploying with stow, and confirming the gateway scheduler picked it up. ## Quick Start Ask the agent to add an OpenClaw cron job with a given job ID, agent ID, schedule type and value, and prompt, then deploy and verify it.

Frequently Asked Questions about openclaw-add-cron

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a cron job to OpenClaw?

Add the job to openclaw.json under cron.jobs with an id, agentId, schedule type and value, and prompt. Then remove ~/.openclaw/cron/jobs.json, deploy with stow, restart the gateway, and verify the job materialized.

What schedule types does OpenClaw support for jobs?

OpenClaw supports three schedule types: cron for cron expressions, every for interval-based recurrence, and at for one-shot timestamps. The schedule.type field must be exactly one of these values.

Why does my OpenClaw cron job break after deployment?

The transient ~/.openclaw/cron/jobs.json file is regenerated by the gateway and can break stow symlink behavior if left in place. Always remove it with rm -f before running stow deployment.

Should OpenClaw scheduled jobs run in isolated sessions?

Yes, isolated execution is the default and recommended setting. Non-isolated cron sessions inflate context cost and cause cross-task leakage between scheduled runs.

How do I verify an OpenClaw cron job was registered?

Query openclaw.json with jq to confirm the job entry exists, then check runtime logs with log show filtered for cron or scheduler messages from the last five minutes.