Claude could start deep research on its own instead of waiting for you to ask, if enabled.
Deep-research model invocation is now decided by gate tengu_sorrel_avocet, which falls back to false, keeping it user-invoked only.
tengu_sorrel_avocet Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.219: 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.
Read once, for one account on one subscription tier, against v2.1.219. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Workflow 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.
- 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. - deep-research previously registered
{ disableModelInvocation: !0 }, meaning user-invocable only. - It now passes a function checking gate
tengu_sorrel_avocetwith fallback false, so absent a remote value behaviour is identical to before. - If the gate is turned on remotely, the model can invoke deep-research itself.
tengu_sorrel_avocet
Strings lifted out of the shipped bundle, so the claim above can be checked against them.