{"version":"2.1.234","anchor":"startup-prefetch-failures-no-longer-surface","canonical_anchor":"startup-prefetch-failures-no-longer-surface","heading":"Startup prefetch failures no longer surface","tier":"notice","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/startup-prefetch-failures-no-longer-surface","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Startup prefetch failures no longer surface\n\nA bad skill or command directory no longer produces a startup error; workflows are pre-warmed too.\n\n**What**\n\nThe startup prefetch now calls a dedicated cache warmer instead of building the full command list. Skill and command loads run together and every failure is swallowed, so a bad skill or command directory no longer produces a startup error. The warmer also pre-loads workflows.\n\n**Details**\n\n- The loads run under a settle-all wrapper inside a try\/catch, and the skills load time is still recorded as a startup phase.\n- Workflow warming short-circuits when workflows are off: the `enableWorkflows` setting set to false, the `CLAUDE_CODE_WORKFLOWS` environment variable set to false, or the `tengu_workflows_enabled` gate (fallback true) off.\n\n**Evidence**\n\n`warmCommandSourceCaches`\n\n- Flag `tengu_workflows_enabled`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.234; this account: on, anonymous baseline: on, compiled default: on)\n- Area: Startup\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}