{"version":"2.1.234","anchor":"dangerous-always-allow-rules-are-set-aside-rather-than-carri","canonical_anchor":"dangerous-always-allow-rules-are-set-aside-rather-than-carri","heading":"Dangerous always-allow rules are set aside rather than carried","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/dangerous-always-allow-rules-are-set-aside-rather-than-carri","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Dangerous always-allow rules are set aside rather than carried\n\nAlways-allow rules matching a dangerous pattern are held aside inactive rather than applied.\n\n**What**\n\nPermission state now pulls rules matching the dangerous pattern out of the active always-allow list into a separate held list, with a path to put them back, so a session can carry those rules without them taking effect.\n\n**Details**\n\n- A companion table records which parts of a session's configuration are stripped this way (`allowed_tools`, `avoid_prompts`, `permission_mode`, `working_directory`) and which are kept as-is.\n\n**Evidence**\n\n`strippedDangerousRules`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}