{"version":"2.1.281","anchor":"permission-state-sanitizer-for-restored-sessions-new-ber-fu","canonical_anchor":"permission-state-sanitizer-for-restored-sessions-new-ber-fu","heading":"Permission-state sanitizer for restored sessions (new ber function)","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/permission-state-sanitizer-for-restored-sessions-new-ber-fu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Permission-state sanitizer for restored sessions (new ber function)\n\nA new step tidies permission settings, including dropping unearned bypass availability and resetting the mode saved before plan mode\n\n**Unclear.** The finding does not say when this step runs, and whether it applies to restored sessions is not shown.\n\n**What**\n\nClaude Code has a new step that tidies up its permission state, the record of which permission mode is in use and which modes are allowed. It does three things:\n\n- It clears a note saying the starting mode was chosen from a proactivity level.\n\n- It marks bypass-permissions mode as unavailable, unless that mode is already active or was allowed by `bypassAvailableByFlag`.\n\n- In plan mode, it resets the mode to return to after planning to \"default\".\n\n**Why**\n\nPermission state carried over from elsewhere does not bring along leftover settings. In particular, it cannot make bypass-permissions mode available when nothing allowed it."}