{"version":"2.1.268","anchor":"internal-codename-ultracode-revealed-for-the-workflow-keyw","canonical_anchor":"internal-codename-ultracode-revealed-for-the-workflow-keyw","heading":"Internal codename 'Ultracode' revealed for the workflow-keyword trigger setting","tier":"use","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/internal-codename-ultracode-revealed-for-the-workflow-keyw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Internal codename 'Ultracode' revealed for the workflow-keyword trigger setting\n\nThe setting that lets the word 'ultracode' start a workflow is now labeled 'Ultracode keyword trigger' in settings\n\n**What**\n\nThe settings panel now shows a row called \"Ultracode keyword trigger\" (setting id `workflowKeywordTriggerEnabled`, on by default). It controls whether typing the word `ultracode` in a prompt automatically starts a [workflow](\/docs\/en\/workflows) \u2014 Claude Code's mode for running a multi-step task across several coordinated agents. Related messages tell you when this happened: \"Dynamic workflow requested for this turn\" when the keyword triggered a workflow, and \"Ultracode keyword ignored for this prompt\" when it didn't.\n\nTurning the setting off lets you type the word `ultracode` in a prompt without it starting a workflow.\n\n**Why**\n\nThis gives a name to a setting that already existed, and a way to type the trigger word for other reasons without it kicking off a workflow you didn't intend to run.\n\n- Area: Workflows\n- Names: `workflowKeywordTriggerEnabled`, `ultracode`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}