{"version":"2.1.281","anchor":"model-fallback-check-accepts-a-responseswapped-signal","canonical_anchor":"model-fallback-check-accepts-a-responseswapped-signal","heading":"Model-fallback check accepts a responseSwapped signal","tier":"internal","area":"Models","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/model-fallback-check-accepts-a-responseswapped-signal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Model-fallback check accepts a responseSwapped signal\n\nThe model-fallback check can now apply the refusal fallback when a response was swapped, not only when a message carries a marker\n\n**Unclear.** The finding does not say what a swapped response is or what the reader sees when this fallback applies.\n\n**What**\n\nClaude Code has a fallback that can apply when the model refuses a request. The helper that decides this now accepts a `responseSwapped` option. The refusal-category fallback can now apply when a response was swapped, and no longer only when the message carries a marker.\n\n**Why**\n\nThe refusal fallback can apply in more situations than before.\n\n- Area: Models\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}