claude-code - 💡(How to fix) Fix [DOCS] Settings page missing "Workflow keyword trigger" setting added in v2.1.157

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…

Fix Action

Fix / Workaround

The only per-prompt workaround offered is:

Code Example

| `disableWorkflowKeywordTrigger` | Prevent the word "workflow" in a prompt from automatically triggering a dynamic workflow. Saved workflows run with `/<name>` still work. Default: `false`. Appears in `/config` as **Workflow keyword trigger**. | `true` |

---

### Stop the keyword from triggering workflows

To stop the word "workflow" in a prompt from automatically launching a dynamic workflow, while keeping saved workflows accessible with `/<name>`:

* Toggle **Workflow keyword trigger** off in `/config`. Persists across sessions.
* Set `"disableWorkflowKeywordTrigger": true` in `~/.claude/settings.json`. Persists across sessions.

When the keyword trigger is disabled, typing "workflow" in a prompt no longer highlights or triggers a workflow run. Saved workflows at `/<name>` and the `/workflows` command remain available.
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

"Available settings" table — the disableWorkflows row and any new row that should be added for the keyword-trigger-specific setting. Also the "Turn workflows off" section at https://code.claude.com/docs/en/workflows.

Current Documentation

The settings page lists only disableWorkflows, which disables dynamic workflows entirely:

disableWorkflows — Disable dynamic workflows and the bundled workflow commands. Default: false. Equivalent to setting CLAUDE_CODE_DISABLE_WORKFLOWS to 1

The workflows page shows a /config toggle that also disables workflows entirely:

Toggle Dynamic workflows off in /config. Persists across sessions.

And describes what happens when workflows are fully disabled:

When workflows are disabled, the bundled workflow commands are unavailable, the workflow keyword no longer triggers a run, and ultracode is removed from the /effort menu.

The only per-prompt workaround offered is:

If Claude Code highlights the word when you didn't mean to trigger one, press alt+w to ignore it for this prompt.

What's Wrong or Missing?

As of v2.1.157, Claude Code added a "Workflow keyword trigger" setting in /config that lets users stop the word "workflow" in a prompt from automatically triggering a dynamic workflow, without disabling workflows entirely.

The settings page does not document this setting or its corresponding JSON key (e.g., disableWorkflowKeywordTrigger or similar). The workflows page does not mention this more granular option — it only describes the all-or-nothing disableWorkflows toggle and the per-prompt alt+w escape.

Users who want to keep workflows available (e.g., running saved workflows with /<name>) but never want the word "workflow" to auto-trigger one have no documented way to configure this. They currently have no choice between "disable everything" and "press alt+w every time."

Suggested Improvement

A. Settings page — add new row to the Available Settings table

Add a row for the new setting between disableWorkflows and editorMode, for example:

| `disableWorkflowKeywordTrigger` | Prevent the word "workflow" in a prompt from automatically triggering a dynamic workflow. Saved workflows run with `/<name>` still work. Default: `false`. Appears in `/config` as **Workflow keyword trigger**. | `true` |

B. Workflows page — update the "Turn workflows off" section

After the existing list of ways to turn workflows off entirely, add a subsection:

### Stop the keyword from triggering workflows

To stop the word "workflow" in a prompt from automatically launching a dynamic workflow, while keeping saved workflows accessible with `/<name>`:

* Toggle **Workflow keyword trigger** off in `/config`. Persists across sessions.
* Set `"disableWorkflowKeywordTrigger": true` in `~/.claude/settings.json`. Persists across sessions.

When the keyword trigger is disabled, typing "workflow" in a prompt no longer highlights or triggers a workflow run. Saved workflows at `/<name>` and the `/workflows` command remain available.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/settingsSettings table row for new disableWorkflowKeywordTrigger setting needed
https://code.claude.com/docs/en/workflows"Turn workflows off" section should mention the keyword-trigger-specific toggle

Total scope: 2 pages affected

Referenced changelog: v2.1.157 — "Added a 'Workflow keyword trigger' setting in /config to stop the word 'workflow' in a prompt from triggering a dynamic workflow"

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 [DOCS] Settings page missing "Workflow keyword trigger" setting added in v2.1.157