{"version":"2.1.323","anchor":"permission-rule-add-refuses-rules-that-look-secret-or-sit-in","canonical_anchor":"permission-rule-add-refuses-rules-that-look-secret-or-sit-in","heading":"Claude Code refuses to save permission rules that look like secrets","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/permission-rule-add-refuses-rules-that-look-secret-or-sit-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude Code refuses to save permission rules that look like secrets\n\nAdding an allow rule is refused if it looks like it holds a secret or the settings file is tracked by git\n\n**What**\n\nAn allow rule is a line in a settings file that lets Claude use a tool without asking you each time. Claude Code now refuses to add one in these cases:\n\n- Looks like a secret: the rule seems to contain a password, key or similar.\n\n- Check failed: the check for secrets could not run.\n\n- Tracked by git: the settings file is tracked by git, so it would be saved into your project's history.\n\nWhen this happens, the rule is not saved and you are told why.\n\n**Why**\n\nIt stops a secret in a permission rule from being written into a file that could get committed and shared.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}