{"version":"2.1.246","anchor":"plan-mode-can-be-restored-by-reading-the-transcript","canonical_anchor":"plan-mode-can-be-restored-by-reading-the-transcript","heading":"Plan mode can be restored by reading the transcript","tier":"notice","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/plan-mode-can-be-restored-by-reading-the-transcript","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Plan mode can be restored by reading the transcript\n\nResuming a session can now re-enter plan mode by reading your transcript, and this is on by default.\n\n**What**\n\nResuming a session could previously only restore plan mode from a value the previous run recorded. A new path instead scans the transcript backwards for plan markers, ExitPlanMode tool calls and plan-mode user turns, classifies the session as still in a plan, exited, or neither, and re-enters plan mode when a plan is open and no recorded mode exists. It is controlled by the `tengu_tranquil_fern` gate, which defaults to on when no server value is present.\n\n**Details**\n\n- Applies only when a `--sdk-url` is used, or when no permission mode was given on the command line; never when forking a session.\n- Tool results that begin with the team-lead submission message, or that carry an awaiting-leader-approval marker, count as still in plan.\n- When it fires, the restore source is recorded as \"transcript\" rather than the previous run's recorded mode.\n- A second latch condition sits alongside the gate, and what it tracks is not determinable from this code path.\n\n**Evidence**\n\n`[planModeResume] re-entering plan mode from the transcript's open plan segment (was `\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}