What
Workflows are Claude Code's multi-step automated runs. Managed settings are settings an administrator puts on a machine that users cannot override. Claude Code now checks managed settings for disableWorkflows, or for CLAUDE_CODE_DISABLE_WORKFLOWS in their env block, and refuses to start a workflow when either is set.
- Refusals now say why. One message covers workflows turned off by the machine's administrator, for example "Code review did not run: workflows are turned off in this machine's managed settings". Another covers managed settings that could not be read.
- The setting's description now reads "Disable the Workflows feature." It adds that Code Review and
/ultrareviewrun in the cloud and are not stopped by it. - The policy check now also takes into account where the session's event came from. It can skip resuming a launch that needs that information.
Why
Administrators get a central way to switch workflows off, and users get a message explaining why a launch was refused. Admins should know the limit: cloud-run Code Review and /ultrareview are not covered by this switch.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear which wins when the environment variable, the setting and the organization's own policy disagree.
Anthropic's release notes agree
Changed Code Review's pull request reviews and /ultrareview to run when disableWorkflows is on, unless the machine running the review has it…