{"version":"2.1.300","anchor":"arbiter-auto-mode-classifier-eligibility-function-with-a-be","canonical_anchor":"arbiter-auto-mode-classifier-eligibility-function-with-a-be","heading":"A check on whether the arbiter classifier can be used, with a retired-beta reason","tier":"internal","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/arbiter-auto-mode-classifier-eligibility-function-with-a-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### A check on whether the arbiter classifier can be used, with a retired-beta reason\n\nClaude Code has a check that can rule out the arbiter classifier, either because a mode doesn't use it or because its beta is retired\n\n**Unclear.** Where this check is used, and so whether it changes anything a user of auto mode sees, is not known.\n\n**What**\n\nIn auto mode, a classifier (a model that judges whether an action should go ahead) can be used to decide on actions. Claude Code now includes a check on whether a mode can use the classifier in its \"arbiter\" role. The check can refuse for either of two reasons:\n\n- The mode's classifier role is not arbiter.\n\n- The arbiter beta has been retired, judged by a separate check on the mode.\n\nIf the check gives no reason, the mode counts as eligible.\n\n**Why**\n\nIn practice, a mode can now be treated as unable to use the arbiter classifier with the stated reason that the arbiter beta has been retired.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}