claude-code - 💡(How to fix) Fix Workflow tool triggers on keyword 'workflow' in normal conversation

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…

Root Cause

This is frustrating because:

  1. "Workflow" is an extremely common English word used in product discussions, UX design, process conversations, etc.
  2. The trigger fires even when the user clearly means "guided user flow" not "multi-agent orchestration script"
  3. There's no way to disable just the keyword trigger while keeping the Workflow tool available for explicit use
  4. disableWorkflows is the only config option but it removes the entire feature
RAW_BUFFERClick to expand / collapse

Problem

The Workflow tool auto-triggers whenever the user's message contains the word "workflow" — even in normal conversation context like "building in more workflows for wired clients" (referring to UI flows, not the multi-agent orchestration tool).

This is frustrating because:

  1. "Workflow" is an extremely common English word used in product discussions, UX design, process conversations, etc.
  2. The trigger fires even when the user clearly means "guided user flow" not "multi-agent orchestration script"
  3. There's no way to disable just the keyword trigger while keeping the Workflow tool available for explicit use
  4. disableWorkflows is the only config option but it removes the entire feature

Expected behavior

The Workflow tool should only activate when the user explicitly requests multi-agent orchestration — e.g., "run a workflow", "use the workflow tool", "fan out agents", "orchestrate this with subagents". Not when "workflow" appears as a normal English word in a sentence about something else.

Suggested fix

Either:

  • Remove the keyword auto-trigger entirely (require explicit invocation)
  • Add a workflowAutoTrigger: false setting to disable the keyword while keeping the tool available
  • Make the trigger smarter (only fire when "workflow" is used in the context of requesting Claude to orchestrate something, not when discussing product features)

Environment

  • Claude Code CLI
  • macOS

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…

FAQ

Expected behavior

The Workflow tool should only activate when the user explicitly requests multi-agent orchestration — e.g., "run a workflow", "use the workflow tool", "fan out agents", "orchestrate this with subagents". Not when "workflow" appears as a normal English word in a sentence about something else.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING