{"version":"2.1.321","anchor":"hidden-path-check-for-dot-prefixed-path-segments","canonical_anchor":"hidden-path-check-for-dot-prefixed-path-segments","heading":"New check for hidden files and folders in permission matching","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/hidden-path-check-for-dot-prefixed-path-segments","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### New check for hidden files and folders in permission matching\n\nClaude Code can now tell whether any part of a path starts with a dot, and its permission path matching gained two early allow rules\n\n**Unclear.** What the two new early allow conditions are, and so which paths no longer need permission, is not clear.\n\n**What**\n\nClaude Code now has a check that looks at each part of a file path and reports whether any of them starts with a dot. Names that start with a dot, such as `.git`, are usually hidden files or folders. This replaces an earlier check for whether a path was safe.\n\nSeparately, the code that decides whether a file path matches a permission rule now allows a path straight away when either of two new conditions holds.\n\n**Why**\n\nThis may change which file paths Claude Code asks your permission for.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}