When fast mode is switched off, it now records why and where from, including hitting extra-usage limits.
What's wrong with this entry?
The fast-mode disabled state now records where the disable came from and distinguishes an overage rejection, and both disable paths avoid redundant app-state writes.
- the disabled state object carries
source: "server" - an overage rejection sets reason
extra_usage_disabledand emits the disabled event - both disable paths skip the app-state write when
penguinModeOrgEnabledis already false - the preference-disable path bails out early only when the existing disabled state came from the server and is not a recoverable reason
extra_usage_disabled
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.234
Search field in the model picker
Both mention model
-
v2.1.236
Cancellable waits when
/modeltalks to a cloud sessionBoth mention model
-
v2.1.238
Model and effort switch warning now checks whether the cache is actually warm
Both mention model