{"version":"2.1.290","anchor":"rewind-telemetry-for-summarized-targets","canonical_anchor":"rewind-telemetry-for-summarized-targets","heading":"Rewind now reports when its target is in summarized history","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/rewind-telemetry-for-summarized-targets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Rewind now reports when its target is in summarized history\n\nRewinding to a point that has been summarized is now tracked separately, and some of those refusals report target not found\n\n**Unclear.** It is not clear whether what you see when a rewind is refused has changed.\n\n**What**\n\nRewind now recognises when the point you want to return to sits inside summarized history, the part of a long conversation that has been compacted into a shorter summary. It records this as `rewind_summarized_target` in its usage data, along with the reason it missed the target.\n\nWhen a rewind is refused because the target would split a tool call (one action Claude takes, such as running a command, together with its result) and that target is in summarized history, the refusal is now reported as `target_not_found`.\n\n**Why**\n\nRewind handles targets in compacted history as their own case, and how often that happens is now measured.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}