{"version":"2.1.305","anchor":"resume-silent-end-turn-reply-after-a-terminal-tool-result-i","canonical_anchor":"resume-silent-end-turn-reply-after-a-terminal-tool-result-i","heading":"Resuming no longer treats a quietly finished turn as interrupted","tier":"soon","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/resume-silent-end-turn-reply-after-a-terminal-tool-result-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Resuming no longer treats a quietly finished turn as interrupted\n\nWhen you resume, a turn that ended right after a tool result with Claude choosing to stop is now treated as complete instead of interrupted\n\n**What**\n\nWhen you resume a conversation, Claude Code looks at how the last turn ended. A tool result is the output of an action Claude ran, such as a command. If the conversation ends on a tool result, Claude's last reply stopped normally, and nothing is still waiting, Claude Code now treats that turn as finished rather than interrupted.\n\nThis is controlled by a server setting. If the server sends no value, Claude Code treats it as on.\n\n**Why**\n\nIt avoids Claude Code offering to continue a turn that had in fact already ended.\n\n- Flag `tengu_vast_journal`: Not enough to say (read for one account on one subscription tier against v2.1.305; 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: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}