What
The checks Claude Code runs on a gateway configuration add two warnings about availableModels, the list of models people are allowed to pick:
- An empty
availableModelslist 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. - 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 whenmodel,enforceAvailableModels,availableModelsMatch: "exact",ANTHROPIC_MODEL,ANTHROPIC_DEFAULT_MODELorANTHROPIC_DEFAULT_OPUS_MODELis set. The warning suggests settingenforceAvailableModels: trueormodel.
Before, the only warning was about aliases in availableModels.
Why
Admins find a setting that would break every developer's requests before rolling it out, rather than after.
Names in the bundleavailableModels
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which command or screen shows these warnings is not confirmed.
Anthropic's release notes agree
Added Claude apps gateway startup warnings when a managed policy's availableModels is empty, or leaves out the model Claude Code starts on…