{"version":"2.1.285","anchor":"remote-sandbox-file-tools-read-only-directories-and-globre","canonical_anchor":"remote-sandbox-file-tools-read-only-directories-and-globre","heading":"Remote sandbox file tools refuse read-only folders and absolute glob patterns","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-sandbox-file-tools-read-only-directories-and-globre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote sandbox file tools refuse read-only folders and absolute glob patterns\n\nIn remote sandboxes, write and edit refuse read-only folders, read can view part of a large file, and glob rejects absolute patterns\n\n**Unclear.** Which environment runs these file tools is not stated.\n\n**What**\n\nClaude Code's file tools, as used in a remote sandbox (an isolated environment where commands run), behave more strictly:\n\n- write and edit: refuse any path inside a read-only folder, saying it \"is inside read-only directory\".\n\n- read: accepts `view_range` for files over the size limit, instead of only telling you to use Bash to read a slice.\n\n- glob: always rejects absolute patterns and asks for a relative one, even where they were allowed before, and caps how many files it scans.\n\n**Why**\n\nThese tools are harder to use against folders or paths they should not touch.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}