Claude Code v2.1.219 ·
fast_mode_disabled_reason on turn-completion telemetry
Turn logs now record why fast mode was skipped, such as env setting or model not allowed.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
TelemetryArea: what it touches
Internal ChangesKind: in v2.1.219,
Internal ChangesSection of the release
What
Turn-completion events now report why fast mode was not used, alongside the existing state field.
Details
- New
fast_mode_disabled_reason sits next to fast_mode_state and is populated from the fast-mode eligibility check. - Values include
not_first_party, disabled_by_env, model_not_allowed, sdk_opt_in_required, pending and unknown. - Present at 18 sites in this build; did not exist in the previous one.
Evidence
fast_mode_disabled_reason
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.219 →
