{"version":"2.1.319","anchor":"resume-a-plan-held-rerun-can-suppress-interrupted-turn-resc","canonical_anchor":"resume-a-plan-held-rerun-can-suppress-interrupted-turn-resc","heading":"Resume holds back re-running a cut-off plan mode turn in another mode","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/resume-a-plan-held-rerun-can-suppress-interrupted-turn-resc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Resume holds back re-running a cut-off plan mode turn in another mode\n\nWith `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` on, a cut-off turn from plan mode is not re-run if the session comes back in another mode\n\n**What**\n\nWhen you resume a session with `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` set, Claude Code can re-run a turn that was cut off. Claude Code now holds that re-run back in one case. The cut-off turn ran in plan mode, where Claude plans without making changes, and the session has come back in a different mode.\n\nThis applies only when no action Claude took in the cut-off turn had returned a result. When the re-run is held back, Claude Code does not try to rescue the interrupted turn. It records an internal notice once at start-up saying why it did not re-run the turn.\n\n**Why**\n\nA resumed session no longer continues a cut-off planning turn on its own after the mode has changed. You decide what happens next instead.\n\n- Flag `tengu_partitioned_finch`: Not enough to say (read for one account on one subscription tier against v2.1.319; 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: Resume\n- Names: `CLAUDE_CODE_RESUME_INTERRUPTED_TURN`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}