Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.219 ·

Bundled workflows can gate model invocation at runtime; deep-research wired to a new flag

Claude could start deep research on its own instead of waiting for you to ask, if enabled.

Nothing to try yet Notable In Development
JSON All of v2.1.219
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
WorkflowsArea: what it touches
In DevelopmentKind: in v2.1.219,
What probably matters to youSection of the release

Deep-research model invocation is now decided by gate tengu_sorrel_avocet, which falls back to false, keeping it user-invoked only.

What

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.

Details
  • 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_avocet with 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.
Evidence

tengu_sorrel_avocet

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/deep-research
Feature flag
tengu_sorrel_avocet Off in both readings

The 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 has happened since
Flag reading moved The flag server now returns off for tengu_sorrel_avocet, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_sorrel_avocet, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_sorrel_avocet

See this entry in the whole of v2.1.219 →

Feedback