{"version":"2.1.234","anchor":"one-place-decides-whether-workflows-are-off","canonical_anchor":"one-place-decides-whether-workflows-are-off","heading":"One place decides whether workflows are off","tier":"use","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/one-place-decides-whether-workflows-are-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### One place decides whether workflows are off\n\nOne helper now decides whether workflows are off, covering the setting, env var and remote gate.\n\n**What**\n\nA single helper now answers whether workflows are disabled, covering the entitlement check, the `enableWorkflows` user setting being false, `CLAUDE_CODE_WORKFLOWS` set to false, and the remote `tengu_workflows_enabled` gate (fallback true). Workflow warm-up returns early when it says so.\n\n**Details**\n\n- Any one of the four conditions is enough to disable workflows; previously these checks were spread across call sites.\n\n**Evidence**\n\n`tengu_workflows_enabled`\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: Workflows\n- Names: `enableWorkflows`, `CLAUDE_CODE_WORKFLOWS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}