{"version":"2.1.283","anchor":"whole-claudestate-directory-added-to-the-sensitive-home","canonical_anchor":"whole-claudestate-directory-added-to-the-sensitive-home","heading":"The whole ~\/.claude\/state folder is now treated as sensitive","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/whole-claudestate-directory-added-to-the-sensitive-home","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### The whole ~\/.claude\/state folder is now treated as sensitive\n\nClaude Code's list of sensitive home-folder paths now covers all of ~\/.claude\/state instead of a few named files inside it\n\n**Unclear.** What this list controls, whether tool access, sandboxing or sync, is not clear.\n\n**What**\n\nClaude Code keeps a list of sensitive paths in your home folder, including places that hold credentials such as `.config\/gh`, `.cargo\/credentials` and `.m2\/settings.xml`. For `~\/.claude\/state`, this list used to name individual files, such as the file that records device consent for MCP servers. It now covers the whole `~\/.claude\/state` folder.\n\n**Why**\n\nAny new consent or state file stored in `~\/.claude\/state` gets the same protection without being listed one by one.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}