{"version":"2.1.227","anchor":"model-roster-flag-can-redirect-refusal-fallback","canonical_anchor":"model-roster-flag-can-redirect-refusal-fallback","heading":"Model roster flag can redirect refusal fallback","tier":"internal","area":"Model Fallback","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/model-roster-flag-can-redirect-refusal-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Model roster flag can redirect refusal fallback\n\nThe server can list models that should be routed differently when a refusal fallback happens.\n\n**What**\n\nA new server-controlled list of model ids now feeds the logic that picks a replacement model after a refusal. Models on the list skip an early exit and are pushed down the fallback path. The list is empty unless the server supplies one, so this has no effect in a default build.\n\n**Details**\n\n- Read from the `tengu_loggia_roster` flag as a JSON array of model ids; anything else logs \"is not a JSON array of model ids; treating it as empty\" and falls back to an empty list.\n\n**Evidence**\n\n`tengu_loggia_roster`\n\n- Flag `tengu_loggia_roster`: Not enough to say (read for one account on one subscription tier against v2.1.227; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Model Fallback\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}