[DOCS] Dynamic workflows docs still describe `ultracode` as the prompt trigger keyword, but v2.1.178 only triggers on explicit phrases

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"Ask for a workflow in your prompt" subsection under "Have Claude write a workflow"

Current Documentation

The workflows guide currently says the ultracode keyword is what triggers a dynamic workflow from a prompt, and that natural-language phrases "also work":

To run a single task as a workflow without changing the session's effort level, include the keyword ultracode in your prompt. Asking in your own words, for example "use a workflow" or "run a workflow", also works: Claude treats a direct request as the same opt-in. Before v2.1.160 the literal trigger keyword was workflow; natural-language requests work in both versions.

The bullet list higher in the same section reinforces this:

* [Ask for a workflow](#ask-for-a-workflow-in-your-prompt) in your prompt, either in your own words or by including the keyword ultracode, and Claude writes one for the task.

The settings table also describes the trigger as a single keyword:

| workflowKeywordTriggerEnabled | Whether the keyword ultracode in a prompt triggers a dynamic workflow. Set to false to type the word without triggering one. The ultracode effort setting, /workflows, and saved workflow commands are unaffected. Default: true. Appears in /config as Ultracode keyword trigger. Added in v2.1.157; before v2.1.160 the trigger keyword was workflow |

The next paragraph (and several other pages) also describe the visual highlight as "violet":

Claude Code highlights the keyword in your input and Claude writes a workflow script for the task instead of working through it turn by turn.

The trigger keyword for [dynamic workflows](/docs/en/workflows) changed from workflow to ultracode; asking for a workflow in your own words still works, and the keyword is highlighted in violet in the prompt

What's Wrong or Missing?

The v2.1.178 changelog states the behavior changed in two ways that the docs do not reflect:

Changed the workflow prompt keyword to use a purple shimmer highlight and trigger only on explicit phrases like "run a workflow" or "workflow:", not on any mention of the word

This contradicts what the docs still say in two places:

A. The trigger is no longer a single keyword

The docs say "include the keyword ultracode in your prompt" — but v2.1.178 says the prompt no longer triggers a workflow on any mention of a single word, only on explicit phrases like "run a workflow" or "workflow:". The example ultracode: audit every API endpoint under src/routes/ for missing auth checks (workflows.md:123) is now misleading: typing ultracode by itself (without the colon) is no longer a trigger, and the new trigger pattern is a leading phrase like "run a workflow" or workflow: followed by content.

The setting name workflowKeywordTriggerEnabled and its description "Whether the keyword ultracode in a prompt triggers a dynamic workflow" no longer match what the setting actually controls in v2.1.178. The /config row name Ultracode keyword trigger is also stale, since the trigger surface is no longer "the keyword ultracode".

B. The visual highlight description is stale

The docs (whats-new/2026-w23.md and the changelog) describe the highlight as "violet", and the workflows page just says "highlights the keyword" without naming a color. v2.1.178 specifies "purple shimmer" — the highlight style changed and the description of how it animates is now missing from the guide.

Suggested Improvement

A. Trigger behavior

Update the "Ask for a workflow in your prompt" subsection so it describes the v2.1.178 behavior:

To run a single task as a workflow, phrase the request explicitly as a workflow request, for example run a workflow: … or workflow: …. Claude Code recognizes the leading phrase and writes a workflow script instead of working through the task turn by turn. Before v2.1.178 the literal trigger keyword was ultracode; before v2.1.160 it was workflow.

The example code block should be updated to use the new trigger pattern, e.g.:

```text theme={null}
workflow: audit every API endpoint under src/routes/ for missing auth checks

The "If you didn't mean to start a workflow…" paragraph already documents the `Option+W` / `Alt+W` and backspace dismiss behavior — that paragraph should be reviewed in the same pass, since dismissing the keyword still implies there is one keyword to dismiss.

### B. Settings table

Update the `workflowKeywordTriggerEnabled` row in the settings table to reflect the new behavior. At minimum:

- Replace "Whether the keyword `ultracode` in a prompt triggers a [dynamic workflow]" with the v2.1.178 description (triggers on explicit phrases, not on any mention of the word).
- Add a `{/* min-version: 2.1.178 */}` note that the trigger surface changed in v2.1.178 from a single keyword to explicit phrases.
- Rename the `/config` row label from **Ultracode keyword trigger** to something that matches the new behavior, e.g. **Workflow phrase trigger**.

### C. Highlight description

Add a one-line note in the "Ask for a workflow in your prompt" section that the matched phrase is rendered with a purple shimmer highlight, so the guide matches the changelog and the existing whats-new entry. Cross-link the `/theme` / `prefersReducedMotion` setting for users who want to disable the animation, since the v2.1.157 changelog called out that the shimmer is supposed to honor "Reduce motion".

### Impact

Medium - Makes feature difficult to understand

### Additional Context


**Affected Pages:**
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/workflows | 114, 121, 123 | Primary trigger description and example |
| https://code.claude.com/docs/en/workflows | 127 | Highlight paragraph (says "highlights the keyword", no color) |
| https://code.claude.com/docs/en/settings | 303 | `workflowKeywordTriggerEnabled` row + `/config` label name |
| https://code.claude.com/docs/en/whats-new/2026-w23 | 86 | Says highlight is "violet"; needs the v2.1.178 purple-shimmer note |
| https://code.claude.com/docs/en/changelog | 304 | Historical "violet" wording (keep historical, but cross-link the updated guide) |

**Total scope:** 5 pages affected.

**Version context:** Behavior described in this issue is current as of v2.1.178 (June 15, 2026). The trigger keyword was renamed from `workflow` to `ultracode` in v2.1.160, then changed to explicit phrases in v2.1.178; the docs currently describe the v2.1.160 state.