Clearing in-session reasoning effort now falls back to your configured effort instead of nothing.
What's wrong with this entry?
Effort is stored as two values, the one the running session picked and the one resolved from CLI flags, environment and settings, with everything reading the session value first and the configured value otherwise. Clearing the in-session effort now falls back to your configured effort instead of to nothing, and a settings-derived effort survives session-level changes.
- The status line, model picker, permission-layer override and the
effort_leveltelemetry field all read through the same resolver. - A helper clears the last-reported effort so the current value gets re-reported after a change.
return e.sessionEffort ?? e.settingsEffort;, sessionEffort
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.239
Effort is now a tagged value resolved against the current model
Both mention effort
-
v2.1.239
Session effort becomes a tagged value
Both mention effort