{"version":"2.1.246","anchor":"detection-of-gateways-that-strip-cache-markers","canonical_anchor":"detection-of-gateways-that-strip-cache-markers","heading":"Detection of gateways that strip cache markers","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/detection-of-gateways-that-strip-cache-markers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Detection of gateways that strip cache markers\n\nClaude Code now spots when a gateway or custom base URL is silently killing your prompt caching.\n\n**What**\n\nFor providers reached through a gateway or a custom base URL, three consecutive turns of 20,000-plus input tokens with no cache read and no meaningful cache creation now report a `cache_coverage_loss` outcome, the signal that something between Claude Code and the model is dropping the cache markers.\n\n**Details**\n\n- Reported under the new `api_prompt_cache_coverage` event, which did not exist in 2.1.245.\n- Fires once per conversation; the first turn that does show cache activity sends a one-shot confirmation instead.\n- Not behind any flag, but limited to non-first-party or custom-endpoint setups.\n\n**Evidence**\n\n`api_prompt_cache_coverage`\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}