Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

Managed-settings disable reason for workflows now covers enableWorkflows: false

Workflows can now also be disabled via 'enableWorkflows: false' set above your own settings

You'll notice Improvements
JSON All of v2.1.280
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.280,
ImprovementsSection of the release
What

Dynamic workflows (Claude Code's feature for running multi-step orchestrations) can be turned off in several ways. The documented list of causes now explicitly includes enableWorkflows: false being set by a settings layer above your own (such as an organization or managed policy), in addition to the existing disableWorkflows setting and the CLAUDE_CODE_DISABLE_WORKFLOWS environment variable.

Why

This clarifies that an admin-level enableWorkflows: false is now a recognized, explained reason workflows might be unavailable to you, rather than appearing unexplained.

Read from
Names in the bundleenableWorkflows
What the documentation says
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up enableWorkflows, on All settings. | [`disableWorkflows`](#disableworkflows) | Turn [dynamic workflows](/docs/en/workflows) off for everyone; use `enableWorkflows` for yourself | Hooks and automation | Any file | settings-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up enableWorkflows, on All settings.

See this entry in the whole of v2.1.280 →

Feedback