[DOCS] Workflows docs still tell users to type `workflow` after the trigger keyword changed to `ultracode`

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

"Have Claude write a workflow" → "Ask for a workflow in your prompt"

Current Documentation

The workflows page currently says:

* Ask for a workflow in your prompt in your prompt with the word workflow, and Claude writes one for the task. To run a single task as a workflow without changing the session's effort level, include the word workflow anywhere in your prompt. Claude Code highlights the word in your input and Claude writes a workflow script for the task instead of working through it turn by turn. If you didn't mean to start a workflow, press Option+W on macOS or Alt+W on Windows and Linux to dismiss the highlight for this prompt, or press backspace while the cursor is right after the highlighted word. To stop the word from triggering at all, turn off Workflow keyword trigger in /config.

The settings reference also says:

workflowKeywordTriggerEnabled — Whether the word workflow in a prompt triggers a dynamic workflow. Set to false to type the word without triggering one. Ultracode, /workflows, and saved workflow commands are unaffected.

What's Wrong or Missing?

In Claude Code v2.1.160, the changelog says:

Renamed the dynamic-workflow trigger keyword from workflow to ultracode. The word workflow no longer triggers a run; asking for one in your own words still works. The trigger keyword is highlighted in violet in the prompt input

The workflows guide and settings reference still document the pre-v2.1.160 behavior.

A. The workflows page tells users to type the wrong trigger keyword

Users following https://code.claude.com/docs/en/workflows are told to include the literal word workflow, but the v2.1.160 behavior changed that trigger keyword to ultracode.

B. The settings reference still describes the old trigger behavior

The workflowKeywordTriggerEnabled row still says it controls whether the word workflow triggers a dynamic workflow. After v2.1.160, that text no longer matches the documented behavior change, so users cannot tell what the setting actually controls.

Suggested Improvement

Update the workflows page and settings reference for v2.1.160+ so they match the current trigger behavior.

Before:

To run a single task as a workflow without changing the session's effort level, include the word workflow anywhere in your prompt.

After:

To run a single task as a workflow without changing the session's effort level, include the word ultracode anywhere in your prompt. You can also ask Claude to run a workflow in plain language without using the trigger keyword literally.

Also update the workflowKeywordTriggerEnabled entry to describe the current keyword behavior explicitly. If the setting name stays the same for compatibility, the docs should say that the key still governs the ultracode trigger keyword.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/workflows | 114-127 | Still says the literal word workflow triggers a dynamic workflow and is the highlighted keyword |
| https://code.claude.com/docs/en/settings | 263 | workflowKeywordTriggerEnabled still says the word workflow triggers a dynamic workflow |

Version evidence:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/changelog | 40 | v2.1.160 says the trigger keyword was renamed from workflow to ultracode, that workflow no longer triggers a run, and that plain-language requests still work |

Total scope: 2 pages affected