{"version":"2.1.202","anchor":"bypasspermissions-mode-not-restored-from-sessions-unless-exp","canonical_anchor":"bypasspermissions-mode-not-restored-from-sessions-unless-exp","heading":"bypassPermissions Mode Not Restored from Sessions Unless Explicitly Launched","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202\/e\/bypasspermissions-mode-not-restored-from-sessions-unless-exp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.202","markdown":"### `bypassPermissions` Mode Not Restored from Sessions Unless Explicitly Launched\n\nWhen restoring a session whose saved permission mode was `bypassPermissions`, Claude Code now checks whether the current session was launched with `--dangerously-skip-permissions` (or the mode is allowed by settings\/policy). If not, it falls back to `default` and logs a warning.\n\n**Details**\n\n- Previously, a restored session could silently inherit dangerous permissions from a prior session\n- The warning logged: \"[externalMetadataToAppState] Refusing restored mode 'bypassPermissions' (disabled by settings\/policy or session not launched with --dangerously-skip-permissions); falling back to 'default'\"\n\n**Evidence**\n\nPermission mode restore guard (search for `\"Refusing restored mode 'bypassPermissions'\"`)"}