{"version":"2.1.292","anchor":"sandbox-read-deny-root-resolution-gets-tracking-state","canonical_anchor":"sandbox-read-deny-root-resolution-gets-tracking-state","heading":"Sandbox keeps more detailed track of read-blocked folders","tier":"internal","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/sandbox-read-deny-root-resolution-gets-tracking-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Sandbox keeps more detailed track of read-blocked folders\n\nThe sandbox now keeps several pieces of progress state while locating folders that commands are blocked from reading\n\n**What**\n\nThe sandbox is a restricted environment that limits what commands run by Claude Code can do, including folders they are blocked from reading. Claude Code used to keep a single yes-or-no marker for when to look for those blocked folders. It now keeps several pieces of state instead:\n\n- whether the first look has happened\n\n- how far the search has got\n\n- when it finished\n\n- whether a failure has been reported\n\n- which blocked folders are within the sandbox's reach\n\n**Why**\n\nThis changes how the sandbox looks for the folders it blocks from reading.\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}