A 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.
- Any one of the four conditions is enough to disable workflows; previously these checks were spread across call sites.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_workflows_enabled On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.