{"version":"2.1.275","anchor":"advisor-model-api-errors-get-dedicated-recognition-includin","canonical_anchor":"advisor-model-api-errors-get-dedicated-recognition-includin","heading":"Advisor-model API errors get dedicated recognition, including org-entitlement case","tier":"internal","area":"Advisor","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/advisor-model-api-errors-get-dedicated-recognition-includin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Advisor-model API errors get dedicated recognition, including org-entitlement case\n\nAdvisor-model API errors are now specifically recognized, including when unavailable for an organization\n\n**What**\n\nNew helper functions now recognize specific 400 errors related to the advisor model: messages saying 'the advisor tool is not available', 'cannot be used as an advisor', or a `tools.N.model` validation error. A further check identifies the specific case where the advisor is unavailable for the caller's organization.\n\n**Why**\n\nThis lets Claude Code identify and presumably handle or report advisor-related errors more precisely, including distinguishing an organization-level entitlement problem from other advisor errors.\n\n- Area: Advisor\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}