{"version":"2.1.299","anchor":"sandbox-literal-path-denies-and-ripgrep-failure-carries-std","canonical_anchor":"sandbox-literal-path-denies-and-ripgrep-failure-carries-std","heading":"Sandbox rules accept literal paths and report ripgrep errors in detail","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/sandbox-literal-path-denies-and-ripgrep-failure-carries-std","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sandbox rules accept literal paths and report ripgrep errors in detail\n\nSandbox read and write lists now accept literal path entries, and ripgrep failures now include its error output and partial results\n\n**What**\n\nThe sandbox limits which files Claude Code may read or write. Its read and write path lists now accept entries that are not plain text, treating them as literal paths. On Windows, Claude Code skips a literal path that no file could have and logs \"Skipping a literal path that no file can have\".\n\nWhen ripgrep (the file search program Claude Code uses) fails, the error now includes ripgrep's error output and any lines it had already found, not just the exit code.\n\n**Why**\n\nSandbox deny rules hold up better against unusual file names, and ripgrep failures are easier to understand.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}