{"version":"2.1.280","anchor":"prompt-cache-diff-tracking-now-covers-thinking-mode-and-thin","canonical_anchor":"prompt-cache-diff-tracking-now-covers-thinking-mode-and-thin","heading":"Prompt-cache diff tracking now covers thinking-mode and thinking-display changes","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/prompt-cache-diff-tracking-now-covers-thinking-mode-and-thin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Prompt-cache diff tracking now covers thinking-mode and thinking-display changes\n\nClaude Code now tracks thinking-mode and thinking-display changes when deciding whether to reuse the prompt cache\n\n**What**\n\nClaude Code keeps an internal record of what changed between requests (things like the model, the system prompt, and the reasoning effort) to decide whether it can reuse the cached prompt or needs to send a fresh one, and to help with diagnostics. This record now also tracks two more fields:\n\n- `thinkingModeChanged`, whether extended thinking mode was turned on or off\n\n- `thinkingDisplayChanged`, whether the display of that thinking changed\n\nBoth fields record the previous and new values, matching how the existing fields already work.\n\n**Why**\n\nSwitching thinking mode on or off, or changing how thinking is displayed, can affect what should be cached. Tracking these changes explicitly lets Claude Code handle the prompt cache correctly around those switches instead of missing them.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}