{"version":"2.1.268","anchor":"model-catalog-now-logs-why-it-fell-back-to-compiled-model-li","canonical_anchor":"model-catalog-now-logs-why-it-fell-back-to-compiled-model-li","heading":"Model catalog now logs why it fell back to compiled model list (credential_scope)","tier":"internal","area":"Model Catalog","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/model-catalog-now-logs-why-it-fell-back-to-compiled-model-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Model catalog now logs why it fell back to compiled model list (credential_scope)\n\nClaude Code now logs a specific reason (credential_scope) when it falls back to the built-in model list due to credential permissions\n\n**What**\n\nWhen the model list Claude Code shows can't be fetched because the current credentials aren't allowed to read the server's model data, it now records a telemetry event, `model_catalog_primary`, with `decision: 'off'` and `off_reason: 'credential_scope'`. The event also logs the HTTP status and refusal code involved, before Claude Code falls back to its built-in, compiled-in list of models.\n\n**Why**\n\nThis makes it possible to tell, from telemetry, specifically when a fallback to the built-in model list happened because of a credential's permissions, rather than some other failure.\n\n- Area: Model Catalog\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}