{"version":"2.1.304","anchor":"sandbox-on-windows-now-computes-filesystem-grants-with-crede","canonical_anchor":"sandbox-on-windows-now-computes-filesystem-grants-with-crede","heading":"Windows sandbox works out its file access from credentials and allowed domains","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-on-windows-now-computes-filesystem-grants-with-crede","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Windows sandbox works out its file access from credentials and allowed domains\n\nOn Windows, the sandbox now uses its credentials and allowed network domains when working out which files it may reach\n\n**Unclear.** Which files the Windows sandbox can now read or write as a result is not stated.\n\n**What**\n\nThe sandbox is a set of limits on what commands run by Claude can reach. On Windows, Claude Code sets it up by working out which files and folders the sandbox is allowed to use. That calculation now also takes the sandbox's credentials and its list of allowed network domains (`allowedDomains`) into account. Before, it was worked out from the sandbox configuration alone.\n\nWhen TLS termination is turned on, setup also runs an extra first step. TLS termination means the sandbox opens up encrypted web traffic so it can be checked.\n\n**Why**\n\nThis could change which files the Windows sandbox is able to read.\n\n- Area: Sandbox\n- Names: `allowedDomains`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}