{"version":"2.1.277","anchor":"model-list-insertion-for-localself-hosted-entries-now-requi","canonical_anchor":"model-list-insertion-for-localself-hosted-entries-now-requi","heading":"Model list insertion for local\/self-hosted entries now requires firstParty context","tier":"internal","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/model-list-insertion-for-localself-hosted-entries-now-requi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Model list insertion for local\/self-hosted entries now requires firstParty context\n\nLocal\/self-hosted model entries now only get added when the context is explicitly first-party\n\n**Unclear.** The finding doesn't explain what problem the previous, looser check caused in practice.\n\n**What**\n\nThe internal check that decides whether to insert a synthesized entry for a local or self-hosted model into the model list now requires an additional condition: the value must be `null` and the context must equal `\"firstParty\"`, on top of the two checks it already required.\n\n**Why**\n\nThis tightens when Claude Code will add a synthesized local\/self-hosted model entry to the list, avoiding cases where it might otherwise show up in the wrong context.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}