{"version":"2.1.299","anchor":"resume-nudge-for-a-cut-off-reply-gated-by-tengu-steady-plov","canonical_anchor":"resume-nudge-for-a-cut-off-reply-gated-by-tengu-steady-plov","heading":"Resuming after a cut-off reply is now recognised as its own case","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/resume-nudge-for-a-cut-off-reply-gated-by-tengu-steady-plov","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Resuming after a cut-off reply is now recognised as its own case\n\nWhen you resume a session whose last reply was recently cut off, Claude Code now treats it as an interrupted turn and can nudge to continue\n\n**Unclear.** It is not clear what you actually see when this nudge applies.\n\n**What**\n\nWhen you resume a session (pick up an earlier conversation), Claude Code checks whether the last turn was interrupted. It now recognises a specific case: the last message is a reply that was recently cut off. In that case it marks the turn as interrupted with a \"cut reply nudge\", rather than handling it like any other message.\n\nThis behaviour sits behind a remotely controlled switch. When the server sends nothing for that switch, Claude Code treats it as on.\n\n**Why**\n\nIt changes what happens when you come back to a session where a reply stopped partway through.\n\n- Flag `tengu_steady_plover`: Not enough to say (read for one account on one subscription tier against v2.1.299; 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: 3\/5\n- Scope: individual\n- Heads-up: no"}