{"version":"2.1.284","anchor":"linux-sandbox-warning-now-also-covers-read-globs-anchored-at","canonical_anchor":"linux-sandbox-warning-now-also-covers-read-globs-anchored-at","heading":"Linux sandbox warning now also flags broad read rules","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/linux-sandbox-warning-now-also-covers-read-globs-anchored-at","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Linux sandbox warning now also flags broad read rules\n\nOn Linux, the sandbox glob warning now also checks `filesystem.denyRead` and `filesystem.allowRead` patterns that start at the root or have no fixed folder\n\n**What**\n\nThe sandbox limits which files commands can read or write. Its rules can use glob patterns, which are wildcards such as `*`. On Linux, Claude Code warns \"Glob patterns in sandbox permission rules are not fully supported on Linux\". That warning now also checks `filesystem.denyRead` and `filesystem.allowRead`. Before, it checked only `filesystem.allowWrite` and `filesystem.denyWrite`.\n\nA pattern is flagged when the fixed part before its first wildcard is empty or just `\/`, as in `**\/.env`. The suggested fix says that on Linux, glob patterns in Edit and Read rules will be ignored.\n\n**Why**\n\nA read rule like `**\/.env` cannot be expanded from a fixed folder on Linux. If you have one, you now get a warning instead of a rule that quietly protects less than you expect.\n\n- Area: Sandbox\n- Names: `filesystem.denyRead`, `filesystem.allowRead`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}