{"version":"2.1.268","anchor":"model-catalog-fetch-now-reports-a-distinct-credential-canno","canonical_anchor":"model-catalog-fetch-now-reports-a-distinct-credential-canno","heading":"Model catalog fetch now reports a distinct 'credential cannot read served list' refusal","tier":"internal","area":"Model Catalog","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/model-catalog-fetch-now-reports-a-distinct-credential-canno","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Model catalog fetch now reports a distinct 'credential cannot read served list' refusal\n\nModel list now reports a specific reason when your credential can't fetch the served catalog\n\n**What**\n\nWhen Claude Code tries to fetch the current list of available models from the server and is refused specifically because the credential in use doesn't have permission to see it, a new handler now fires a `model_catalog_primary` telemetry event recording the decision as 'off' with the reason `credential_scope`, and prints a console note explaining that the built-in, compiled-in model list is being used instead.\n\n**Why**\n\nThis makes it clearer, both to telemetry and to the user via the console note, why the served model list wasn't used and the fallback list is in effect, distinguishing it from other kinds of fetch failures.\n\n- Area: Model Catalog\n- Names: `credential_scope`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}