You could set an effort level per model in settings, but the lookup is gated off.
modelSettings.<model>.effortLevel is written and read behind a flag falling back to false.
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.239: on
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Any settings layer can set modelSettings.<model>.effortLevel, which overrides the top-level effortLevel for that one model, with model ids normalised before lookup. Saving effort to user settings writes both the top-level key and the per-model entry. The lookup is gated on tengu_russet_plover, which falls back to false, so absent a server value the per-model table stays empty and effort behaves exactly as before.
- Session effort is now a tagged value: an explicit level, the default, or inherited.
tengu_russet_plover
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.240
"Switch your default effort to medium?" prompt, complete but with no text to show
Both mention effort level
-
v2.1.240
Saving a default effort level can now scope it to one model
Both mention effort level
-
v2.1.240
Telemetry for the effort nudge
Both mention effort level