{"version":"2.1.286","anchor":"compact-model-fallback-triggered-events-thrown-and-fallback","canonical_anchor":"compact-model-fallback-triggered-events-thrown-and-fallback","heading":"Conversation compaction handles a switch to a backup model differently","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/compact-model-fallback-triggered-events-thrown-and-fallback","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Conversation compaction handles a switch to a backup model differently\n\nWhen compaction hits a switch to a backup model, it now raises that as an error and can put the current model back into the backup list\n\n**Unclear.** It is not clear what condition decides whether the current model is put back into the backup list.\n\n**What**\n\nCompaction is when Claude Code summarizes a long conversation to free up room. Claude Code can fall back to a backup model when the one it asked for is not available. During compaction, a signal that such a switch happened is now raised as an error. When an error is caught, Claude Code can, under some conditions, put the current model back into its list of backup models. Before, compaction handled only requests to fall back.\n\n**Why**\n\nThis may change how well compaction copes when the model switches to a backup.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}