Always-allow rules matching a dangerous pattern are held aside inactive rather than applied.
What's wrong with this entry?
Permission 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.
- 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.
strippedDangerousRules
Strings lifted out of the shipped bundle, so the claim above can be checked against them.