{"version":"2.1.239","anchor":"resuming-a-session-that-was-in-plan-mode-puts-you-back-in-pl","canonical_anchor":"resuming-a-session-that-was-in-plan-mode-puts-you-back-in-pl","heading":"Resuming a session that was in plan mode puts you back in plan mode","tier":"notice","area":"Plan Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/resuming-a-session-that-was-in-plan-mode-puts-you-back-in-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Resuming a session that was in plan mode puts you back in plan mode\n\nResuming a session that was in plan mode now puts you back in plan mode.\n\n**What**\n\nWhen you resume a session whose previous run was in plan mode, Claude Code now re-enters plan mode instead of starting in whatever mode the caller asked for. The guard is the remote flag `tengu_tranquil_fern`, which falls back to on, so this is active unless the server turns it off. It is skipped when forking a session and when the permission layer refuses.\n\n**Details**\n\n- The session records its permission mode into internal metadata; on resume, if the recorded mode was plan and the live context is not, the permission context is forced to plan with source \"internal\".\n- Recording is latched: a call made during resume setup arms it, and permission-mode changes emit the metadata only once armed, so sessions that never went through that path record nothing.\n- Also requires the plan-presentation tool to be enabled.\n- An unrecognized recorded mode is logged and ignored rather than applied.\n- Telemetry `tengu_worker_permission_mode_restore` reports source, lane, trusted mode, recorded mode, target mode and whether the guard was on.\n\n**Evidence**\n\n`[planModeResume] ignoring unrecognized internal_metadata.worker_permission_mode`, `tengu_worker_permission_mode_restore`\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}