{"version":"2.1.323","anchor":"trust-check-now-covers-multiple-directories","canonical_anchor":"trust-check-now-covers-multiple-directories","heading":"Folder trust checks now use the git repository root and flag unsafe paths","tier":"notice","area":"Workspace Trust","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/trust-check-now-covers-multiple-directories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Folder trust checks now use the git repository root and flag unsafe paths\n\nClaude Code's folder trust check now looks at the git repository root, applies an unsafe-path rule, and reports more detail\n\n**What**\n\nBefore Claude Code works in a folder, it checks whether you have marked that folder as trusted. If you have not, it asks you first. That check used to look at a single directory. It now also uses the root of the git repository (the top folder of the project's version history) and applies a rule for paths it considers unsafe.\n\nThe check now reports four things:\n\n- `trusted`: whether the location counts as trusted\n\n- `directory`: the folder that was checked\n\n- `unsafe_path`: whether the path was judged unsafe\n\n- `root`: the root folder used for the check\n\n**Why**\n\nThis could change when Claude Code shows the trust prompt. If you start Claude Code inside a git project, trust may be decided by the project's root folder rather than only the folder you are in.\n\n- Area: Workspace Trust\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}