{"version":"2.1.295","anchor":"upstream-models-list-requires-at-least-one-entry","canonical_anchor":"upstream-models-list-requires-at-least-one-entry","heading":"A models list on an upstream must have at least one entry","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/upstream-models-list-requires-at-least-one-entry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### A models list on an upstream must have at least one entry\n\nClaude Code now rejects an empty models list on an upstream and says to remove the key to send every model\n\n**Unclear.** Which configuration file or feature this upstream models list belongs to is not stated.\n\n**What**\n\nClaude Code now checks a configuration setting that lists models on an upstream. If the list is empty, it reports an error saying that a models list on an upstream needs at least one entry. The message also says that to send every model, you should remove the key entirely instead of leaving the list empty.\n\n**Why**\n\nThis points to a setting that limits which models are sent to a given upstream. An empty list is now treated as a mistake and is not read as \"no models\".\n\n- Area: LLM Gateway\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: yes"}