{"version":"2.1.232","anchor":"cache-diagnostics-no-longer-imply-a-model-switch-that-did-no","canonical_anchor":"cache-diagnostics-no-longer-imply-a-model-switch-that-did-no","heading":"Cache diagnostics no longer imply a model switch that did not happen","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cache-diagnostics-no-longer-imply-a-model-switch-that-did-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cache diagnostics no longer imply a model switch that did not happen\n\nCache diagnostics say \"hydrated baseline\" instead of falsely implying you switched models.\n\n**What**\n\nWhen Claude Code explains why a prompt cache was invalidated, it now prints `hydrated baseline` if the thing it compared against was reconstructed at startup rather than an actual earlier request, instead of naming a previous model or removed beta flags.\n\n**Evidence**\n\n`hydrated baseline`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}