{"version":"2.1.292","anchor":"sidequery-can-drop-cache-control-when-caching-is-disabled","canonical_anchor":"sidequery-can-drop-cache-control-when-caching-is-disabled","heading":"Background model requests can strip cache markers when caching is off","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/sidequery-can-drop-cache-control-when-caching-is-disabled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Background model requests can strip cache markers when caching is off\n\nExtra background requests to the model can now remove prompt-caching markers when the model has caching turned off, and log that they did\n\n**What**\n\nBesides your main conversation, Claude Code sometimes sends smaller side requests to the model. These side requests have a new option, `dropCacheControlWhenCachingDisabled`. When it is set and the model in use has prompt caching turned off, Claude Code removes the cache markers from the request. Prompt caching lets the API reuse earlier parts of a conversation instead of processing them again. When markers are removed, Claude Code writes a log line saying they were dropped because prompt caching is off.\n\nBefore, cache markers were always sent as they were. API usage from these requests is now also added up per host and per thread.\n\n**Why**\n\nSending cache markers to a model that has caching off can cause API errors or wasted work. Stripping them avoids that.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}