{"version":"2.1.223","anchor":"model-switches-invalidate-the-cached-prewarm-entry","canonical_anchor":"model-switches-invalidate-the-cached-prewarm-entry","heading":"Model switches invalidate the cached prewarm entry","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/model-switches-invalidate-the-cached-prewarm-entry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Model switches invalidate the cached prewarm entry\n\nSwitching models now throws away prewarm work done for the old model instead of finishing it stale.\n\n**What**\n\nChanging models now discards any precomputed prewarm work tied to the previous model instead of letting it complete against stale state.\n\n**Details**\n\n- Both the app-state model change handler and the remote model-switch path call the precompute-cache invalidator with the reason `model_switch`.\n- Any in-flight prewarm is aborted with an AbortError named for that reason.\n- Same mechanism previously used only for `subagent_exit`.\n\n**Evidence**\n\n`l_t(void 0, \"model_switch\")`\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}