What
The description of CronCreate, the tool Claude uses to schedule tasks for later, was rewritten in this release in the prompt used by the team onboarding command in the SDK. The description explains that the scheduler shifts run times slightly:
- Repeating tasks can fire up to 10% of their interval late, at most 15 minutes
- One-time tasks set for :00 or :30 can fire up to 90 seconds early
Why
These details tell Claude what to expect from the scheduler, which affects the times it chooses and what it tells you about when a task will run.
Names in the bundleCronCreate
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up CronCreate, on Use the mods API.
| [`$.tool.call`](/docs/en/plugins/mods/reference#mods-api-methods) of Bash with `run_in_background: true`, Monitor, or CronCreate | Resolves with `{ deny: '<tool> was not run: it starts background work, a schedule or a goal, and <reason>'…plugins/mods/api see the edit
Added since
A small documentation edit on Error reference touched a line naming CronCreate after this was published.
* For a tool that [background subagents drop](/docs/en/sub-agents#available-tools), such as `CronCreate`, remove the entryerrors see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Error reference touched a line naming CronCreate after this was published.