{"version":"2.1.314","anchor":"resume-interrupted-turn-that-ended-on-context-rows-is-treat","canonical_anchor":"resume-interrupted-turn-that-ended-on-context-rows-is-treat","heading":"Resumed sessions that had already finished replying are no longer nudged to continue","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/resume-interrupted-turn-that-ended-on-context-rows-is-treat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Resumed sessions that had already finished replying are no longer nudged to continue\n\nWhen a resumed session had already finished replying, Claude Code no longer adds a prompt telling the model to continue\n\n**What**\n\nResuming a session means picking up an earlier conversation where it left off. If the conversation looks like it was cut off, Claude Code adds a prompt asking the model to continue.\n\nClaude Code now skips that prompt in one case. The case is a conversation where all of these are true:\n\n- It ends with background context rather than a reply.\n\n- No action is still waiting for its result.\n\n- Its last rows show only a queued note with no real work after it.\n\nThis is controlled by a setting that is on unless it is switched off remotely.\n\n**Why**\n\nYou should see fewer extra turns started on their own when you resume a session that had already finished replying.\n\n- Flag `tengu_partitioned_finch`: Not enough to say (read for one account on one subscription tier against v2.1.314; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}