Fast mode unavailability is tracked as reason codes internally, feeding clearer messages and telemetry.
What's wrong with this entry?
The check for why Fast mode is unavailable now returns a code rather than an English sentence, with a separate function that turns the code into the user-facing text.
- Codes include
not_first_party,disabled_by_env,model_not_allowed,sdk_opt_in_required,pending, plus server-supplied reasons such asextra_usage_disabled. - Telemetry gains a
fast_mode_disabled_reasonfield with a schema enum for the codes. - The org-status cache records provenance as
source: "guess"orsource: "server", and only emits a change event when the value or the reason actually changed.
sdk_opt_in_required
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.221
Fast mode credit rejections show a notification instead of silently turning fast mode off
Both mention fast mode model
-
v2.1.221
Fast mode no longer offered on Opus 4.7
Both mention fast mode model