{"version":"2.1.288","anchor":"api-cache-breakpoint-marks-a-parent-reply","canonical_anchor":"api-cache-breakpoint-marks-a-parent-reply","heading":"The end of a parent prompt can be marked as a prompt-cache breakpoint","tier":"internal","area":"Prompt Cache","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/api-cache-breakpoint-marks-a-parent-reply","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### The end of a parent prompt can be marked as a prompt-cache breakpoint\n\nClaude Code can now mark where a parent prompt ends as a prompt-cache breakpoint, which affects how often cached prompts are reused\n\n**Unclear.** It is not clear which parts of Claude Code turn this marking on.\n\n**What**\n\nClaude Code reuses parts of earlier requests to the model through a prompt cache, which stores a prompt's opening so it does not have to be processed again. A cache breakpoint is a marked point in the prompt up to which the cache can be reused.\n\nClaude Code can now mark the end of a parent prompt, meaning the prompt that started a piece of work, as one of these breakpoints. This is controlled by an optional setting inside Claude Code. The usage data Claude Code records about cache breakpoints now also notes where a request came from and whether the parent prompt's end was marked.\n\n**Why**\n\nWhere breakpoints sit decides how much of a prompt can be reused from the cache, so this can change how often requests are served from it.\n\n- Area: Prompt Cache\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}