Map, prioritize and schedule all your OpenClaw automations in one place. Assign agents, set triggers, estimate monthly token costs, detect scheduling conflicts and export a ready-to-paste cron config block for your openclaw.json.
| Task | Model | Runs/mo | Est. Cost |
|---|
// Add automations above\n// to generate config
The OpenClaw Automation Planner is a free visual planning board for organizing, scheduling and costing all your OpenClaw AI automations before deploying them. Instead of manually tracking which cron jobs run at what time, which agent handles each task and how much each automation costs per month, this tool puts everything in one visual dashboard.
It generates a ready-to-paste cron block for your openclaw.json β with correct agent IDs, prompts, concurrency settings and sandbox flags. It also shows a 24-hour timeline so you can visually space out heavy tasks and avoid the most common OpenClaw problem: too many concurrent jobs exhausting context windows and burning API quota simultaneously.
maxConcurrentRuns queues overflow jobs, but a queue of 8 heavy jobs with 30-minute timeouts each means the last job runs 4 hours lateThe planner estimates monthly cost using real 2026 model pricing. It multiplies estimated tokens per run by the model's per-token rate, then multiplies by the number of runs per month based on the cron schedule. The estimates are conservative β they assume 60% input / 40% output token split and do not account for caching discounts.
maxConcurrentRuns setting in the cron block controls how many cron jobs run at the same time. The safe default is 2β3. Running more than 4 concurrent heavy jobs risks context window exhaustion, API rate-limit errors and runaway token costs. Jobs beyond the limit are queued β they run as soon as a slot opens. This planner lets you configure maxConcurrentRuns and shows which jobs will be queued at peak overlap times.maxConcurrentRuns: 2 as a safety limit β queuing is safer than parallel exhaustion.~/.openclaw/openclaw.json file and replace (or merge) the existing cron block with the exported block. Then run openclaw doctor --fix to validate the schema and openclaw gateway restart if the cron section was previously empty. Cron changes hot-reload without a restart if the gateway was already running with cron enabled.