{"version":"2.1.299","anchor":"windows-sandbox-native-deny-entries-written-and-renewed-wi","canonical_anchor":"windows-sandbox-native-deny-entries-written-and-renewed-wi","heading":"Windows sandbox now writes and renews its own file-blocking rules","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/windows-sandbox-native-deny-entries-written-and-renewed-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Windows sandbox now writes and renews its own file-blocking rules\n\nOn Windows, the sandbox now installs and renews its file deny rules itself; set CLAUDE_CODE_SANDBOX_LEAVE_DENIES_TO_SRT_WIN to turn this off\n\n**What**\n\nThe sandbox is a fenced-off environment that limits which files and network addresses commands run by Claude Code can reach. On Windows, Claude Code now writes the sandbox's deny rules (the list of paths commands may not touch) itself, through a built-in native command. It also renews them while it runs. If renewal fails, Claude Code stops with an error and reports that the rules were not renewed.\n\nTo switch this off, set the environment variable `CLAUDE_CODE_SANDBOX_LEAVE_DENIES_TO_SRT_WIN`. Claude Code checks it at startup and, when it is set, leaves the deny rules to the sandbox runtime, srt-win, as before.\n\nClaude Code also expands wildcard patterns in deny and allow paths, and it now takes symbolic links (shortcuts that point to another file or folder) into account when it does.\n\n**Why**\n\nThis changes how Windows sandbox file protections are enforced. If the new behaviour causes problems, the environment variable lets you go back to the old one.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}