{"version":"2.1.219","anchor":"bundled-workflows-can-gate-model-invocation-at-runtime-deep-","canonical_anchor":"bundled-workflows-can-gate-model-invocation-at-runtime-deep-","heading":"Bundled workflows can gate model invocation at runtime; deep-research wired to a new flag","tier":"soon","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/bundled-workflows-can-gate-model-invocation-at-runtime-deep-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Bundled workflows can gate model invocation at runtime; deep-research wired to a new flag\n\nClaude could start deep research on its own instead of waiting for you to ask, if enabled.\n\n**What**\n\nWorkflow registration accepts a function for `disableModelInvocation`, and the bundled deep-research workflow now uses one so a remote flag can decide whether the model may invoke it.\n\n**Details**\n\n- When converting a workflow to a command the code checks `typeof e.disableModelInvocation === \"function\"` and calls it; v2.1.218 only ever read a boolean.\n- deep-research previously registered `{ disableModelInvocation: !0 }`, meaning user-invocable only.\n- It now passes a function checking gate `tengu_sorrel_avocet` with fallback false, so absent a remote value behaviour is identical to before.\n- If the gate is turned on remotely, the model can invoke deep-research itself.\n\n**Evidence**\n\n`tengu_sorrel_avocet`\n\n- Flag `tengu_sorrel_avocet`: Off in both readings (read for one account on one subscription tier against v2.1.219; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Workflows\n- Names: `\/deep-research`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}