{"version":"2.1.278","anchor":"third-party-classifier-availability-check-reworked","canonical_anchor":"third-party-classifier-availability-check-reworked","heading":"Third-party classifier availability check reworked","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278\/e\/third-party-classifier-availability-check-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.278","markdown":"### Third-party classifier availability check reworked\n\nThe check for whether the server-side auto-mode classifier can be used was reworked internally\n\n**Unclear.** It's unclear from the evidence what the new predicate and the swapped function actually change in terms of which providers qualify.\n\n**What**\n\nThe function that gates whether the server-side auto-mode classifier is usable changed its handling of third-party providers: it now checks a new predicate on the resolved provider, and calls a different negated function than before when deciding availability.\n\n**Why**\n\nThis is an internal change to how third-party providers are evaluated for server-side classifier eligibility; the finding doesn't specify what practical difference it makes for users.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}