Auto mode now shows a dialog explaining when a session isn't eligible for classifier billing changes, with telemetry to match
What
- Claude Code now shows a new dialog when auto mode's tool-call classifier falls back from the server-side classifier to the local one. It tells you Claude Code is changing auto mode to stop charging for classifier requests, but explains that your current session isn't eligible for that change, so this classifier request is still billed as before.
- The dialog appears when the server-side (third-party) classifier has already been refused earlier in the session and a tool call falls back to the local, billed classifier. You can press Enter to continue (and accept the billed request) or Escape to cancel the tool call, which is recorded with the reason "Cancelled at the classifier billing notice."
- New analytics events were added to track when the server-side classifier fails to return a result and auto mode falls back to local classification, and when this new billing notice is shown or closed.
Why
This makes it clear to users when a specific auto-mode session still incurs classifier billing despite an upcoming change to stop charging for these requests, and gives them the choice to cancel rather than proceed with a billed request they didn't expect.
tengu_velvet_heron Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.278: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.278. It isn't a statement about your account. What a flag value here can and cannot tell you
The three related gates (`tengu_velvet_heron`, `tengu_auto_mode_server_fallback_notice`, `tengu_auto_mode_server_fallback_notice_closed`)…
New in this build: tengu_velvet_heron