{"version":"2.1.309","anchor":"compact-summaries-tracked-when-finding-the-last-human-turn","canonical_anchor":"compact-summaries-tracked-when-finding-the-last-human-turn","heading":"Claude Code can still find your last message after a conversation is compacted","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/compact-summaries-tracked-when-finding-the-last-human-turn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude Code can still find your last message after a conversation is compacted\n\nWhen looking back for the last user turn, Claude Code now falls back to details saved in the most recent compaction summary\n\n**Unclear.** It is not clear what Claude Code then does with the recovered turn start, so the visible effect is unknown.\n\n**What**\n\nCompaction is when Claude Code shortens a long conversation by replacing older messages with a summary. Claude Code sometimes looks back through the conversation for the user turn that decides what happens next. While it does this, it now also notes the most recent compaction summary. If it finds no such turn, it falls back to where that turn started, using information stored with the summary. Before, it returned nothing about that turn in this case.\n\n**Why**\n\nAfter a conversation has been compacted, Claude Code can still locate the previous user turn even though the original messages were replaced by a summary.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}