Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.285 ·

Workflows off switch now enforced from managed settings, with clearer limits

Admins can turn workflows off through managed settings with disableWorkflows or CLAUDE_CODE_DISABLE_WORKFLOWS; cloud Code Review and /ultrareview are not stopped

Group of 2 Use it now Improvements
JSON All of v2.1.285
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
ImprovementsKind: in v2.1.285,
What probably matters to youSection of the release

Unclear Whether how the setting is enforced also changed, or only its description, is not clear.

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 /ultrareview run 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.

Read from
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.

Added since A small documentation edit on Code Review touched a line naming /ultrareview after this was published. To run a cloud review from a script or CI job, use the [`claude ultrareview` subcommand](/docs/en/ultrareview#run-ultrareview-non-interactively), which waits for the findings and prints them to stdout. code-review see the edit
Confirmed since Anthropic's documentation has since written up /ultrareview, on Claude Code changelog. * Removed the browser link from `/ultrareview` and `claude ultrareview` output changelog see the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether how the setting is enforced also changed, or only its description, is not clear.
Anthropic's documentation agreesAnthropic's documentation has since written up /ultrareview, on Claude Code changelog.
Anthropic's release notes agreeFixed a misleading "core.worktree is set" error from /ultrareview when the project folder briefly could not be read

See this entry in the whole of v2.1.285 →

Feedback