Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

One place decides whether workflows are off

Use it now
Useful3 Signal3
Workflows Notable not in their notes

One helper now decides whether workflows are off, covering the setting, env var and remote gate.

Feature flag
tengu_workflows_enabled Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.234: off

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

enableWorkflowsCLAUDE_CODE_WORKFLOWS
What

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.

Details
  • Any one of the four conditions is enough to disable workflows; previously these checks were spread across call sites.
Evidence

tengu_workflows_enabled

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.

See this entry in the whole of v2.1.234 →