Your saved default effort could apply per model instead of everywhere, but that is off.
Per-model effort defaults are implemented behind the tengu_russet_plover gate; with it off you still get one global setting.
tengu_russet_plover 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.240: on
Read once, for one account on one subscription tier, against v2.1.240. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
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.
- 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.
{ effortLevel: t, modelSettings: { [r]: { effortLevel: t } } }
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Effort display names ultracode and warns about the environment override
Both mention effort level
-
v2.1.239
Per-model effort level in settings, behind a gate
Both mention effort level
-
v2.1.239
New
modelSettingsconfig key holds per-model effortBoth mention effort level