{"version":"2.1.311","anchor":"doctor-reports-permission-rules-that-may-not-work-as-written","canonical_anchor":"doctor-reports-permission-rules-that-may-not-work-as-written","heading":"\/doctor now flags permission rules that may not work as written","tier":"use","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/doctor-reports-permission-rules-that-may-not-work-as-written","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### `\/doctor` now flags permission rules that may not work as written\n\n`\/doctor` and the warnings list gain a section headed \"Permission rules that may not work as written\"\n\n**What**\n\nPermission rules are settings that let Claude do some things without asking, or stop it from doing them. `\/doctor`, the command that checks your Claude Code set-up, and the list of warnings now include a section headed \"Permission rules that may not work as written\".\n\n**Why**\n\nA rule that silently does nothing can leave you thinking something is allowed or blocked when it is not. This section brings those rules to your attention.\n\n- Area: Permissions\n- Names: `\/doctor`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}