{"version":"2.1.238","anchor":"schedule-no-longer-fetches-your-environments-just-to-preload","canonical_anchor":"schedule-no-longer-fetches-your-environments-just-to-preload","heading":"\/schedule no longer fetches your environments just to preload","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/schedule-no-longer-fetches-your-environments-just-to-preload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### \/schedule no longer fetches your environments just to preload\n\nPreloading `\/schedule` no longer makes network calls to fetch your environments and repositories.\n\n**What**\n\nLoading 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.\n\n**Details**\n\n- Gated on an `isSkillPreload` flag on the command context; a real run still fetches as before.\n- The environment fetch now receives the storage handle it needs rather than reaching for it.\n\n**Evidence**\n\n`Environment and repository details are resolved when the skill is actually run.`\n\n- Area: Slash Commands\n- Names: `\/schedule`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}