claude-code - 💡(How to fix) Fix [FEATURE/QUESTION] How to enable Workflow tool? CLAUDE_CODE_WORKFLOWS=1 set but tool doesn't surface (GrowthBook gate?)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

The 2.1.147 changelog says:

"Added the Workflow tool for deterministic multi-agent orchestration. It is off by default — set CLAUDE_CODE_WORKFLOWS=1 to enable."

I've set CLAUDE_CODE_WORKFLOWS=1 and confirmed it's in the Claude process env (via ps eww), running v2.1.149 on macOS. The Workflow tool does not appear in the session tool surface. I've also confirmed .claude/workflows/*.workflow.js files are present at session boot.

Root Cause

The 2.1.147 changelog says:

"Added the Workflow tool for deterministic multi-agent orchestration. It is off by default — set CLAUDE_CODE_WORKFLOWS=1 to enable."

I've set CLAUDE_CODE_WORKFLOWS=1 and confirmed it's in the Claude process env (via ps eww), running v2.1.149 on macOS. The Workflow tool does not appear in the session tool surface. I've also confirmed .claude/workflows/*.workflow.js files are present at session boot.

Code Example

function bp() {
  if (!mH(process.env.CLAUDE_CODE_WORKFLOWS)) Dw_ = false;
  else Dw_ = k_("tengu_workflows_enabled", true);
  return Dw_;
}
RAW_BUFFERClick to expand / collapse

Summary

The 2.1.147 changelog says:

"Added the Workflow tool for deterministic multi-agent orchestration. It is off by default — set CLAUDE_CODE_WORKFLOWS=1 to enable."

I've set CLAUDE_CODE_WORKFLOWS=1 and confirmed it's in the Claude process env (via ps eww), running v2.1.149 on macOS. The Workflow tool does not appear in the session tool surface. I've also confirmed .claude/workflows/*.workflow.js files are present at session boot.

Investigation

Inspecting the binary, the gate logic is:

function bp() {
  if (!mH(process.env.CLAUDE_CODE_WORKFLOWS)) Dw_ = false;
  else Dw_ = k_("tengu_workflows_enabled", true);
  return Dw_;
}

The env var passes. k_("tengu_workflows_enabled", true) appears to call GrowthBook, and since none of the `Pv()` bypass triggers are set (no `DISABLE_TELEMETRY`, `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`, etc.), GrowthBook is active. The `tengu_workflows_enabled` flag appears to evaluate to `false` for my account.

Question

Is this feature currently in a limited beta requiring explicit account enablement? If so, how do I request access? I'm building multi-agent YLO (YouTube Launch Optimizer) workflows and have a realistic use case ready to test immediately (replicating a working bespoke blackboard-conductor pattern as a native workflow for comparison).

Environment

  • Claude Code v2.1.149
  • macOS (Apple Silicon), Max plan
  • `CLAUDE_CODE_WORKFLOWS=1` confirmed in process env
  • `.claude/workflows/hello.workflow.js` and `title-gen.workflow.js` present at session boot
  • No `DISABLE_TELEMETRY`, `DISABLE_NONESSENTIAL_TRAFFIC`, or `DISABLE_GROWTHBOOK` set
  • `ToolSearch select:Workflow` returns no match

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [FEATURE/QUESTION] How to enable Workflow tool? CLAUDE_CODE_WORKFLOWS=1 set but tool doesn't surface (GrowthBook gate?)