{"version":"2.1.288","anchor":"model-catalog-document-can-carry-a-minimum-claude-code-versi","canonical_anchor":"model-catalog-document-can-carry-a-minimum-claude-code-versi","heading":"Model catalog can require a minimum Claude Code version","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/model-catalog-document-can-carry-a-minimum-claude-code-versi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Model catalog can require a minimum Claude Code version\n\nThe hosted model catalog can now name a minimum Claude Code version that older builds skip, and failed first cloud messages now give a clearer reason\n\n**Unclear.** Whether any model list currently sets a minimum version is not established.\n\n**What**\n\nClaude Code downloads a hosted model catalog, a document describing the available models and their settings. Before, the catalog was accepted whatever Claude Code version you ran.\n\n- The catalog can now include an optional `min_claude_code_version` field.\n\n- The download step now checks your build's version against that field. If the catalog needs a newer version, the download fails with `below_minimum_version` and older builds skip that catalog.\n\n- When the first message to a cloud session fails to send, the error now explains the reason in words, such as the service being busy. Before, it printed the raw reason in parentheses.\n\n**Why**\n\nAn older Claude Code no longer tries to read a model catalog written for newer builds. If your first message to a cloud session fails, the error now tells you more clearly why.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}