What
Loading the schedule skill without running it no longer calls out to fetch your environments and repositories. It emits a note instead, so preloading costs no network round trips.
Details
- Gated on an
isSkillPreloadflag on the command context; a real run still fetches as before. - The environment fetch now receives the storage handle it needs rather than reaching for it.
Evidence
Environment and repository details are resolved when the skill is actually run.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/schedule
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.
Added since
A small documentation edit on Common workflows touched a line naming /schedule after this was published.
| [`/loop`](/docs/en/scheduled-tasks) | The current CLI session | Quick polling while a session is open. `--resume` and `--continue` restore unexpired fixed-interval loops. |common-workflows see the edit
Confirmed since
Anthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop.
| | [Cloud](/docs/en/routines) | [Desktop](/docs/en/desktop-scheduled-tasks) | [`/loop`](/docs/en/scheduled-tasks) |desktop-scheduled-tasks see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /schedule, on Schedule recurring tasks in Claude Code Desktop.