{"version":"2.1.282","anchor":"prompt-cache-marker-added-at-the-point-a-forked-request-dive","canonical_anchor":"prompt-cache-marker-added-at-the-point-a-forked-request-dive","heading":"Forked requests get a prompt-cache marker where they branch off","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/prompt-cache-marker-added-at-the-point-a-forked-request-dive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Forked requests get a prompt-cache marker where they branch off\n\nWhen a request branches off a conversation, Claude Code now marks the cache just before the point where it diverges\n\n**Unclear.** It is not clear which requests supply the point of divergence, so how often this applies is unknown.\n\n**What**\n\nThe prompt cache lets the model reuse parts of a conversation it has already processed instead of reading them again. Claude Code marks where cacheable parts end.\n\nFor a fork, a request that branches off an existing conversation, Claude Code can now place an extra marker just before the reply where the branch diverges. When it does, it skips the older way of pinning the fork point.\n\n**Why**\n\nThis changes which part of a forked request can be reused from the cache. Whether it saves anything in practice depends on which requests use it.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}