{"version":"2.1.310","anchor":"model-picker-availability-of-customserver-listed-models-re","canonical_anchor":"model-picker-availability-of-customserver-listed-models-re","heading":"Custom and server-listed models: wider validity check and reworked \/model picker list","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/model-picker-availability-of-customserver-listed-models-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Custom and server-listed models: wider validity check and reworked \/model picker list\n\nModel ids are now checked against two settings maps, and the \/model picker can swap a disabled entry for an enabled one from the server\n\n**Unclear.** It is not clear what decides when the merging happens, so it is unclear which entries you will now see.\n\n**What**\n\nTwo parts of how Claude Code handles models beyond the standard list changed:\n\n- Checking a model id: the check that a model id is known now uses a new helper. It compares cleaned-up ids against the text values in two settings maps. Before, it looked at only one map and cleaned up the ids differently.\n\n- The `\/model` picker list: the code that builds the picker's entries now takes a condition and merges entries from the server into the list in place. A disabled entry can be replaced by an enabled one that matches it. Before, server entries were only added at the end when they were missing.\n\n`ANTHROPIC_CUSTOM_MODEL_OPTION_DESCRIPTION`, the setting that labels the custom model entry in the picker, is part of the list-building code that changed.\n\n**Why**\n\nSome model choices that were rejected before may now be accepted, and the `\/model` picker may show different entries, with a usable version of a model taking the place of a disabled one.\n\n- Area: Models\n- Names: `\/model`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}