{"version":"2.1.323","anchor":"workflow-tool-describessystemturns-option-and-whentouse-tex","canonical_anchor":"workflow-tool-describessystemturns-option-and-whentouse-tex","heading":"Workflow tool gets clearer guidance on when Claude should use it","tier":"notice","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/workflow-tool-describessystemturns-option-and-whentouse-tex","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Workflow tool gets clearer guidance on when Claude should use it\n\nThe Workflow tool now tells Claude to use it only when the user asked, ultracode is confirmed, or a skill or command calls for it\n\n**What**\n\nThe Workflow tool lets Claude run a coordinated set of subagents, which are helper copies of Claude that each take part of a task. Its description now includes guidance on when to use it:\n\n- The user has asked in their own words to orchestrate subagents.\n\n- A notice confirms \"ultracode\", the keyword or session mode that asks for this.\n\n- A skill or command the user invoked calls for it.\n\nIf a task would merely benefit from it, Claude is told to use another approach or ask instead.\n\nIn the stock Workflow description captured under v2.1.323, the lines about ultracode now say a \"message from the system\" confirms it, where the v2.1.322 capture said a \"system-reminder\".\n\n**Why**\n\nIt changes how Claude decides whether to start a multi-agent workflow, so it should do so mainly when you have asked for one.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}