{"version":"2.1.300","anchor":"third-party-model-config-new-mindesktopversion-and-1m-seman","canonical_anchor":"third-party-model-config-new-mindesktopversion-and-1m-seman","heading":"Third-party model settings gain a minimum app version and a new 1M context rule","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/third-party-model-config-new-mindesktopversion-and-1m-seman","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Third-party model settings gain a minimum app version and a new 1M context rule\n\nThird-party model setups can set a minimum Desktop version, and the 1M setting now uses 1M context wherever it's available\n\n**What**\n\nThese changes affect the model settings an organization uses to offer models through a third-party setup.\n\n- A new `minDesktopVersion` field, shown as \"Minimum app version\", greys a model out in Claude Desktop apps older than that version.\n\n- The \"Default to 1M context\" setting is now \"Use 1M wherever it\u2019s available\". Before, it only started the model picker on the 1M version of the default model. 1M context is a model version that can take in about a million tokens of text at once.\n\n- With `prefer1m` set, the picker now shows only the 1M version of a model.\n\n- Several of these model settings are now read by Claude Code as well as by Claude Desktop.\n\n**Why**\n\nOrganizations using third-party setups get a different rule for when 1M context is chosen, and Claude Code now follows these settings too.\n\n- Area: Managed Settings\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}