Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Effort LevelsArea: what it touches
In DevelopmentKind: in v2.1.240,
What probably matters to youSection of the release
Per-model effort defaults are implemented behind the tengu_russet_plover gate; with it off you still get one global setting.
What
Previously, saving a default effort wrote both a global setting and a per-model one. With the tengu_russet_plover gate on, it now writes only the per-model entry, so the default applies to the model you are using rather than everything. With the gate off, which is the built-in default, it writes only the global setting.
Details
The gate is remote, tengu_russet_plover, fallback off.
Model names that would collide with built-in JavaScript object property names also fall back to the global-only write.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Read from
Feature flag
tengu_russet_ploverOff 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.240: off
Flag reading movedThe flag server now returns on for tengu_russet_plover, 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 movedThe flag server now returns nothing at all, having stopped carrying it for tengu_russet_plover, 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.
