[DOCS] Workflow docs do not state that `/deep-research` requires explicit invocation
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/workflows
Section/Topic
The bundled-workflow description and “Run a bundled workflow” instructions for /deep-research.
Current Documentation
The page currently says:
The quickest way to see a workflow in action is to run /deep-research...
and instructs the user:
Run /deep-research with a question you want investigated.
It explains the workflow phases and approval prompt, but does not explicitly say whether Claude may start this workflow automatically from a task request.
What's Wrong or Missing?
Claude Code 2.1.218 changed /deep-research to start only when the user invokes it manually; Claude no longer launches it on its own.
The workflow guide explains how to invoke the command but does not document this explicit-only contract. Users who rely on the general workflow or skill invocation behavior cannot tell whether mentioning a research task is enough to launch /deep-research, or whether they must type the command.
Suggested Improvement
Add a versioned note near the bundled-workflow table:
/deep-researchstarts only after you invoke it explicitly. Claude does not launch this bundled workflow automatically from a research request. Type/deep-research <question>when you want the workflow to run.
Clarify that the approval step described below occurs after explicit invocation and that this rule is specific to the bundled /deep-research command, not to user-authored workflows that Claude may recommend.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/workflows | Bundled /deep-research invocation and approval flow |
| https://code.claude.com/docs/en/commands | Command discovery and invocation semantics |
Total scope: 2 pages should state the explicit-invocation contract.
The behavior was changed in Claude Code v2.1.218.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗