{"version":"2.1.166","anchor":"fallbackmodel-setting-in-settings-json","canonical_anchor":"fallbackmodel-setting-in-settings-json","heading":"fallbackModel setting in settings.json","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166\/e\/fallbackmodel-setting-in-settings-json","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.166","markdown":"### `fallbackModel` setting in settings.json\n\n**What**\n\nThe fallback model list can now be set in `settings.json` as an array, not only via `--fallback-model` on the command line.\n\n**Usage**\n\n`# Via CLI (comma-separated, as before) claude --fallback-model sonnet,haiku # Via settings.json (new \u2014 array form) # In ~\/.claude\/settings.json or project .claude\/settings.json: # { \"fallbackModel\": [\"sonnet\", \"haiku\"] }` **Details** - Accepts model name aliases such as `\"sonnet\"`, `\"haiku\"`, or `\"default\"` (which expands to the current default model) - CLI `--fallback-model` takes precedence over the setting - The setting is also available in managed settings for enterprise deployments - Models that are not recognized or not available in the current context are silently skipped **Evidence** New `fallbackModel` schema field (search for `'Fallback model(s) tried in order when the primary model is overloaded or unavailable'`)"}