{"version":"2.1.284","anchor":"gateway-config-validation-warns-about-empty-or-default-less","canonical_anchor":"gateway-config-validation-warns-about-empty-or-default-less","heading":"Gateway config checks warn about model lists that would reject every request","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/gateway-config-validation-warns-about-empty-or-default-less","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Gateway config checks warn about model lists that would reject every request\n\nGateway checks now warn when availableModels is empty or leaves out the default model, both of which get requests refused\n\n**Unclear.** Which command or screen shows these warnings is not confirmed.\n\n**What**\n\nThe checks Claude Code runs on a gateway configuration add two warnings about `availableModels`, the list of models people are allowed to pick:\n\n- An empty `availableModels` list in managed settings (settings an organization installs centrally). Claude Code reads an empty list as \"Default model only\", but the gateway checks requests against the list itself, so every request is rejected.\n\n- A list that leaves out the model Claude Code starts on by default. Developers then get a 400 error (a rejected request) on every request until they choose a listed model with `\/model`. No warning is given when `model`, `enforceAvailableModels`, `availableModelsMatch: \"exact\"`, `ANTHROPIC_MODEL`, `ANTHROPIC_DEFAULT_MODEL` or `ANTHROPIC_DEFAULT_OPUS_MODEL` is set. The warning suggests setting `enforceAvailableModels: true` or `model`.\n\nBefore, the only warning was about aliases in `availableModels`.\n\n**Why**\n\nAdmins find a setting that would break every developer's requests before rolling it out, rather than after.\n\n- Area: Gateway\n- Names: `availableModels`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}