{"version":"2.1.278","anchor":"new-request-latch-state-for-server-side-classifier-fallback","canonical_anchor":"new-request-latch-state-for-server-side-classifier-fallback","heading":"New request-latch state for server-side classifier fallback and gateway tracking","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/new-request-latch-state-for-server-side-classifier-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### New request-latch state for server-side classifier fallback and gateway tracking\n\nSession state now tracks the inference gateway seen and any classifier fallback choice made\n\n**What**\n\nClaude Code's internal per-session state object gained new tracking for the auto-mode server classifier fallback:\n\n- which inference gateway was observed for the session\n\n- whether a fallback choice was made when the server-side classifier is unavailable, and what that choice was\n\n- a one-shot flag for announcing that fallback to the user (so the announcement only happens once)\n\n- whether the third-party server classifier was refused for this session\n\n**Why**\n\nThis gives the new server-classifier fallback and billing-notice features a place to remember what's already happened in a session, so users aren't shown the same fallback notice repeatedly or asked to re-decide something already settled.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}