{"version":"2.1.317","anchor":"windows-sandbox-records-deny-lists-given-at-start","canonical_anchor":"windows-sandbox-records-deny-lists-given-at-start","heading":"The Windows sandbox notes which block rules it was given at start","tier":"internal","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/windows-sandbox-records-deny-lists-given-at-start","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### The Windows sandbox notes which block rules it was given at start\n\nOn Windows, the sandbox now keeps a record of the read and write block lists it was given when it started\n\n**What**\n\nThe sandbox is the restricted space Claude Code runs commands in. On Windows, in some setups, it now keeps a record of the blocked-read and blocked-write path lists it was handed when it started.\n\n**Why**\n\nThis is record-keeping for the Windows sandbox's block rules.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}