You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Plan ModeArea: what it touches
In DevelopmentKind: in v2.1.246,
What probably matters to youSection of the release
What
Resuming 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.
Details
Applies only when a --sdk-url is used, or when no permission mode was given on the command line; never when forking a session.
Tool results that begin with the team-lead submission message, or that carry an awaiting-leader-approval marker, count as still in plan.
When it fires, the restore source is recorded as "transcript" rather than the previous run's recorded mode.
A second latch condition sits alongside the gate, and what it tracks is not determinable from this code path.
Evidence
[planModeResume] re-entering plan mode from the transcript's open plan segment (was
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
