Skip to content
← Back to release · 2.1.283
New features / v2.1.283

Add deniedModels managed setting

CHANGELOG · original

Added deniedModels managed setting to block specific models, even when availableModels allows them
Open official changelog ↗

Documentation

Documentation excerpt

deniedModels

Block specific models, with or without an availableModels allowlist and even when that list permits them. Claude Code hides a blocked model from the /model picker, and the model can't be selected anywhere availableModels is enforced. A session on the Default option doesn't run a blocked model either, as Block specific models or versions describes. Requires Claude Code v2.1.283 or later.

  • Scope: Managed. Claude Code ignores the key in user, project, and local settings and in --settings, with a warning
  • Type: array of model aliases or IDs
    • A family alias such as "opus" blocks every model in that family
    • A model ID such as "claude-opus-5-5" blocks that version in every spelling, including dated and provider-specific IDs
    • A model ID with no minor version, such as "claude-opus-5", also blocks later minor versions such as Opus 5.5. Write "claude-opus-5-0" to block Opus 5 alone
    • best, opusplan, and default entries are ignored
  • Default: unset, so no model is blocked

This example permits Opus and Sonnet models and blocks Opus 5.5:

{
  "availableModels": ["opus", "sonnet"],
  "deniedModels": ["claude-opus-5-5"]
}

See Block specific models or versions.

Documentation snapshot · 2026-11-20

Change details