{"version":"2.1.299","anchor":"deny-glob-and-settings-error-messages-reworded","canonical_anchor":"deny-glob-and-settings-error-messages-reworded","heading":"Deny-pattern and settings-read error messages are reworded","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/deny-glob-and-settings-error-messages-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Deny-pattern and settings-read error messages are reworded\n\nMessages about deny patterns ending in a separator and about unreadable settings now use new wording, and the settings one is more general\n\n**Unclear.** It is not clear whether deny patterns now match differently or only the message changed.\n\n**What**\n\nTwo messages have new wording:\n\n- Deny rule patterns ending in a path separator such as `\/`. The warning now says such a pattern can match no path as a pattern, and that the name is also read as the path of that name where it exists. A deny rule is a setting that blocks Claude from certain files.\n\n- Settings that fail to load. The error now says \"your settings could not all be read\", where before it said your Read rules or sandbox settings could not all be read. It now refers to an administrator's settings instead of managed settings.\n\n**Why**\n\nThe new wording suggests such a deny pattern may also match a file or folder with that exact name, and that the settings error now covers more than Read rules. If you use deny patterns that end in a separator, check that they block what you expect.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}