{"version":"2.1.257","anchor":"signed-remote-model-catalog-published-catalog-infrastruc","canonical_anchor":"signed-remote-model-catalog-published-catalog-infrastruc","heading":"Signed remote model catalog ('published catalog') infrastructure","tier":"notice","area":"Model Catalog","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/signed-remote-model-catalog-published-catalog-infrastruc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Signed remote model catalog ('published catalog') infrastructure\n\nThe model list, aliases and defaults can now come from a signed remote catalog document rather than only from app releases.\n\nClaude Code can now fetch, cache, and verify a signed remote \"model catalog\" document from `https:\/\/downloads.claude.ai\/model-catalog\/v1\/catalog.json` (or a custom\/managed URL). Signatures use RSASSA-PKCS1-v1_5-SHA512 checked against trust roots, with a hard-coded release-signing public key named `claude-code-release-signing-key`, and a compiled-in seed document is used as a fallback before the first successful fetch. This lets the model list, aliases, and defaults be updated server-side rather than only through app releases, with tamper protection from the signature check.\n\n- Area: Model Catalog\n- Names: `CLAUDE_CODE_MODEL_CATALOG_URL`\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 5\/5"}