Parse a cron expression (5 or 6 fields) and compute next runs in a time zone with DST, plus an Arabic and English description
OpenClaw Automation Planner
Enter automation tasks (name | cron | agent | input tokens | output tokens) and your price per million tokens to estimate runs and cost per task and agent and detect conflicts in the same minute.
Workspace
How the result is calculated
For each task a five-field cron is parsed (lists, ranges, steps, names and macros; OR between day-of-month and day-of-week when both are restricted) and every run is counted in a window of N days from the start date in UTC. Run cost = input ÷ 10⁶ × input price + output ÷ 10⁶ × output price, period cost = cost × number of runs, summed per agent. A conflict: two tasks of the same agent run in the same minute.
Limits:
Prices and token counts are your inputs and no figures are embedded (they go stale); the estimate ignores context caching, agent tools and retries. Time is UTC only with no time zones. A conflict does not mean an actual failure; it depends on how your system handles agent concurrency. It does not know OpenClaw’s official schema and does not connect to it.
FAQ
Where do I get prices?
From your model provider’s pricing page; enter them yourself.
Is a conflict an error?
Not necessarily; your agent may support concurrency.
