Preloading /schedule no longer makes network calls to fetch your environments and repositories.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command