{"version":"2.1.305","anchor":"model-fallback-notice-finder-for-the-transcript","canonical_anchor":"model-fallback-notice-finder-for-the-transcript","heading":"Model fallback notices are matched more strictly","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/model-fallback-notice-finder-for-the-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Model fallback notices are matched more strictly\n\nClaude Code now reports a fallback-model switch only when the reply came from the fallback model and not the original\n\n**What**\n\nWhen Claude Code switches to a fallback model (a backup model used when the chosen one is unavailable), it leaves a notice in the conversation. The way it looks for that notice changed. It searches back from the latest message and reports a fallback only when Claude's reply came from the fallback model and that model differs from the original one. Placeholder replies and replies that were API errors are skipped.\n\n**Why**\n\nIt affects when Claude Code tells you it has switched to a fallback model.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}